I don't know if this is a network security/permissions problem or an Access problem, but heregoes:
A client had 4 machines, 3 running Win2K & A2K and 1 running WinXP & A2002. The split db worked just fine under that scenario, no version conflicts.
Client upgraded the 3 machines to WinXP and A2003. They also changed servers (could have done some server-side stuff I am not aware of). Access 2003 will open by clicking the shortcut icon in the All User's start folder, but I cannot start Access by clicking the MSAccess.exe icon in the Program Files\Microsoft Office\Office folder. It gives me an error: "This application must be installed to run. Please run setup from where you originally installed the application". This does not happen on the older machine with WinXP and A2002.
This is important because I use a shortcut to start the .mdb because I use an .mdw. It seems to not like starting the MSAccess.exe directly, like clicking on the .exe icon or referencing it in the shortcut.
BTW, the .mdb is still in A2000 format.
Any thoughts?
Jay
A client had 4 machines, 3 running Win2K & A2K and 1 running WinXP & A2002. The split db worked just fine under that scenario, no version conflicts.
Client upgraded the 3 machines to WinXP and A2003. They also changed servers (could have done some server-side stuff I am not aware of). Access 2003 will open by clicking the shortcut icon in the All User's start folder, but I cannot start Access by clicking the MSAccess.exe icon in the Program Files\Microsoft Office\Office folder. It gives me an error: "This application must be installed to run. Please run setup from where you originally installed the application". This does not happen on the older machine with WinXP and A2002.
This is important because I use a shortcut to start the .mdb because I use an .mdw. It seems to not like starting the MSAccess.exe directly, like clicking on the .exe icon or referencing it in the shortcut.
BTW, the .mdb is still in A2000 format.
Any thoughts?
Jay