Search results

Right now I think it's differences between 2000 and 2003. I'm going to put the 2000 runtime on the server and see what happens. Installing the 2000 runtime allowed me to run 2 copies of the mdb no problem. The third attempt to run appears to have timed out. I'm starting to think it's a...

Thanks for the info. RemoteApp is set up with a batch file that opens the MDB. I'm betting that it's putting the ldb in the same folder once one person runs it so I guess that's the problem. However, it use to run in Terminal Server with multiple people using a desktop short cut to the same...

Figured out the problems. There's a 32bit ODBC in the SYSWOW64 folder. Had to put the ODBC there. There was a connection string pointing to a name that some genius had in the Hosts file instead of using machine name or IP. That caused the DBNETLIB error.

Have a MDB written for Access 2000 run time for Terminal Server. I moved it to Server 2008 and the 2003 Runtime. Up and running with a few growing pains. We then published it through RemoteApp. RemoteApp is not allowing multiple RemoteApp instances to run. If I open it on the server and...

I have two Access front ends for SQL Server 2000 written a million years ago. They have been running on Server 2000 Terminal Server with an Access 2000 runtime for TS. I now need to move them to Windows 2008 and SQL 2008. I moved them both to Windows 7 64bit with a minimum of difficulty...