As you guessed, you probably need to add the location of the mdb as a trusted location in IE (Internet Explorer) under the Security tab for every user if you want to automate this in code. Otherwise there was a post a few weeks ago on vb code to bypass the trusted zone settings in IE but I wasn't sure if that code would work in vba. But I think the problem is that it must run a type of procedure that's normally done manually and runs 'outside so to speak' the MSAccess environment and thus needs to look at if it can excecute that procedure in the trusted zone setup for the user (controlled in IE).
For example, for users to run a vb script, they would need to be setup (trusted zone in IE) to point to the network drive to execute a vb script against that network drive since security of the vb script is contained within IE for executing of the vb script within the trusted zone.
I would second-guess why though that you need to convert/build the application on the fly since again, as NTC pointed out, you don't necessarily need to do the conversion for the user to open the mdb file (2007 will open previous versions without conversion.) I'd only do what you're doing if the frontends where on user's desktops and there were specific problems since upgrading an mdb to a new version usually entails some sort of recoding/fixing somewhere (actual conversions rarely go completely smooth without some fixing of code somewhere.) I wouldn't recommend trying to do these on the fly in code as the user opens the mdb file.
Also make sure ALL your users have WRITE and READ permissions to the folder as this causes a locked *.ldb file (or corruption as you may term it.)
You need to define what you mean by corruption as I also think you're using the wrong approach. For example, trying to convert an mdb file while someone else is in that same mdb file will have undesirable affects.
Last edited by pkstormy; 11-07-09 at 00:32.
Expert Database Programming
MSAccess since 1.0, SQL Server since 6.5, Visual Basic (5.0, 6.0)