Multi User Form - Different Service Packs

[mpspeer]

I need a form to be on a server so multiple users (11) can access it.

Earlier, I ran in to the SP1 issue where my VBA was corrupted, but I was able to recover the DB.

I know I obviously need to split the DB in order to secure future data if something happens again (thankfully this was a dry-run that resulted in this), but am wondering how can I set this form up so that users with different Service Packs do not corrupt the form/vba?

Let me know if you need more info and thanks!

 

[mdlueck]

You would benefit from:

1) Software Distribution to deploy the FE DB down to the client machine and then execute the FE DB from there.

FE AutoUpdate with RoboCopy / XCopy
http://www.access-programmers.co.uk/forums/showthread.php?p=1214733#post1214733

2) Use this process to prep a new copy of the FE DB prior to deployment:

NT Command Script and Documented Steps to Decompile / Compact / Compile an Access DB
http://www.access-programmers.co.uk/forums/showthread.php?t=219948

Success deploying completely decomplied database to both Access 2007 and Access 2010
http://www.access-programmers.co.uk/forums/showthread.php?p=1217193#post1217193

 

[mpspeer]

This brings up another question of mine: Is the different versions of Access the only thing that would make that error/corruption appear? It's all I have noticed when researching, but just had a colleague of mine try it (who has a different access version (14.0.6123.5001 (32-bit) to my 14.0.4760.1000 (32-bit)) and it did not corrupt anything with a few test runs. I guess it could be possible that there is a mysterious 3rd version being used...

 

[mdlueck]

This brings up another question of mine: Is the different versions of Access the only thing that would make that error/corruption appear?

No, using one version of Access can quickly grunge a database file. Thus I included the instructions to clean up a database file. Perhaps it is merely grunged.