Fatal error in VBA connect

[vanessa03]

Macola 7.6.300, SQL 2000, Terminal Server 2000
We have just set up a terminal server site. All seems to be working well until a user runs a program that has VBA code attached (screenset is also modified). As soon as the program lauches, she get a message box with "Fatal Error in VBA Connect". We are scratching our heads. Flex is installed on the terminal server and we have given full access to registry keys for macola and odbc. We have also installed new MDAC. The program works fine when you sign on with same user locally, so it has to be with the terminal server. I would appreciate any help. Thanks.

 

[kscheeler]

Does the user Administrator work from the terminal server?

Kevin Scheeler

 

[abaldwin]

The users need full access to the c:\temp directory of the terminal server.

Easiest way to manage this in my opinion is to create a Domain group called MacolaUsers or whatever and add all the macola users to that group. Then give the group access to the Terminal Servers Temp directory.

Andy


Andy Baldwin

 

[vanessa03]

No, the administrator account does not work. We have given (or so we think) full rights to all users. We have done so many changes on this terminal server that we think something must be messed up. We threw together another test terminal server. After reintalling Macola & Flex with VBA errors, we used Macola Doc#01.053.669(copying the install VBA directory to the terminal server) to fix the problem. Then Macola worked fine on this test server. However when we did the same on our production server, it still didn't work. We are probably going to end up rebuilding the production terminal server, because we just can't find the solution. Thanks for your help.