AgentSmith
Well-known Member
- Joined
- Mar 8, 2004
- Messages
- 575
Bit of a long shot, this, I must admit. With a bit of luck perhaps someone browsing this forum may have come across the same thing.
In our company there is 1 department that makes extensive use of AtRisk, a stochastic simulation plug-in for Excel provided by Palisade Software. Our guys have 1 spreadsheet in particular that requires AtRisk and is absolutely vital to their work.
To date they have been using Windows XP, Office 2003 and AtRisk version 4.5. They are migrating to Vista, Office 2007 and a newer version of AtRisk (probably 5.5). The mission critical spreadsheet will not work on the new spec machine. It generates error messages along these lines:
"The function Dtools Version did not register properly"
"ExtractLibraryDatatoWorksheet did not register properly"
...and eventually Excel crashes.
We have been in touch with Palisade tech support who have made numerous suggestions about potential fixes and our IT department have been involved throughout. However I have just come from a conference call where we showed them the problems using a desktop sharing application. Their latest idea is that it is due to the 2 GB memory limit of Excel 2007. Frankly I don't believe it. I've done some searching and found that Excel 2007 can use twice as much memory as Excel 2003, so it doesn't make sense to me.
I'm just hoping to stumble across someone who knows the answer!
In our company there is 1 department that makes extensive use of AtRisk, a stochastic simulation plug-in for Excel provided by Palisade Software. Our guys have 1 spreadsheet in particular that requires AtRisk and is absolutely vital to their work.
To date they have been using Windows XP, Office 2003 and AtRisk version 4.5. They are migrating to Vista, Office 2007 and a newer version of AtRisk (probably 5.5). The mission critical spreadsheet will not work on the new spec machine. It generates error messages along these lines:
"The function Dtools Version did not register properly"
"ExtractLibraryDatatoWorksheet did not register properly"
...and eventually Excel crashes.
We have been in touch with Palisade tech support who have made numerous suggestions about potential fixes and our IT department have been involved throughout. However I have just come from a conference call where we showed them the problems using a desktop sharing application. Their latest idea is that it is due to the 2 GB memory limit of Excel 2007. Frankly I don't believe it. I've done some searching and found that Excel 2007 can use twice as much memory as Excel 2003, so it doesn't make sense to me.
I'm just hoping to stumble across someone who knows the answer!
