T
tommapdotnet
I hope this is the correct forum. We have a legacy app which was originally
written for Access v4 and Win95 and C++. It has migrated without many
problems up to Access 2000 and XP, but now we are having a specific issue
with Access 2003 (and probably anything newer). The C++ program (v5) spawns
the Access application with a CreateProcess command. The application
parameter is obviously MSAccess which fires up OK, but the CommandLine
parameter holding the application and some other attributes is being totally
ignored. The CreateProcess is returning success, but the Access application
is not loading. Using the same command line from a desktop shortcut works
fine. So what has changed between Access 2000 and Access 2003 to stop this
CreateProcess from operating correctly?
written for Access v4 and Win95 and C++. It has migrated without many
problems up to Access 2000 and XP, but now we are having a specific issue
with Access 2003 (and probably anything newer). The C++ program (v5) spawns
the Access application with a CreateProcess command. The application
parameter is obviously MSAccess which fires up OK, but the CommandLine
parameter holding the application and some other attributes is being totally
ignored. The CreateProcess is returning success, but the Access application
is not loading. Using the same command line from a desktop shortcut works
fine. So what has changed between Access 2000 and Access 2003 to stop this
CreateProcess from operating correctly?