N
nightowlky
Doing support for a new client and they are trying to run an application
remotely (thru a Term Serv session) that hits an .mdb file. Doing so
results in the error above and "operation is not allowed when the object is
closed".
Running the .EXE and hitting the .mdb from a mapped drive across a vpn to
the server runs fine. The exe has its own installation process that appears
to want to install such things as various controls along with ADO and OLEDB
DLLs. I have to go to Control Panel...Add/Remove Programs...Add New Program
to install it which goes just fine. Checking around the
%systemroot%\system32 and \program files\common files\system shows newer
DLLs than the install program contains. Could this be affecting the
operation of the app? I'm unsure what the app was written in but my guess
is VB 6.
remotely (thru a Term Serv session) that hits an .mdb file. Doing so
results in the error above and "operation is not allowed when the object is
closed".
Running the .EXE and hitting the .mdb from a mapped drive across a vpn to
the server runs fine. The exe has its own installation process that appears
to want to install such things as various controls along with ADO and OLEDB
DLLs. I have to go to Control Panel...Add/Remove Programs...Add New Program
to install it which goes just fine. Checking around the
%systemroot%\system32 and \program files\common files\system shows newer
DLLs than the install program contains. Could this be affecting the
operation of the app? I'm unsure what the app was written in but my guess
is VB 6.