We just updated from Windows Server 2003 to Server2008. I’ve a process I’ve coded with VB in access which, using a ‘shell’ command to run the command prompt and startanother copy of Access, now fails, whereas it ran fine for a couple of years under server 2003.
The new problem which is occurring, is that the database (“ItemBatch.accdb”)will start just fine if it’s standalone. But if any other user has opened it, the shell run command fails, just ‘blips’at me. It seems to know it’s opened by another process. The ItemBatch.accdb is set up for multiuser, and like I said has been running for some time with multiple users accessing it.
The Shell command I’m using is:
Shell "cmd.exe /c Start ""Item Batch processing"" ""F:\Access\MyFolder\ItemBatch.accdb""", vbNormalFocus
I’m reading that it may be security policy from the first command prompt (shell) executing a 2nd command (start), and that it may not carry the same domain policy to the 2nd command. I can’t find any way to carry domain policy from one command prompt to another.
Anyone with ideas or a resolution? Or a different approach?
I just want to be able to execute an Access database fromwithin VB code of my primary database and it run normally.