[Micromax]

[ScottGem]

By using it. Access by default is set up as a multi-user platform. If the Access app is stored on a network share, multiple users can open it simultaneously. Nothing more needs to be done, but more should be done.

EVERY access app that will be used by more than one user should be split into a back end (the tables) and a front end (everything else). The back end goes on the network share and the front ends are stored locally on the users computers. Access includes a Splitter wizard that will create the back end for you and create the links in the front end.

[Micromax]

Hi Scott. Nice to hear from you and thanks for replying. I haven't used the splitter thus far. I guess If people are not on a network and I split the database, I'm assuming I can tell prospects that the database.mdb file, is allowed on a multi-user level. If I understand this correctly, the buyer needs not to worry about anything once the database is in their possession, because I would split the database from my end. Hope I'm right?

[ScottGem]

If you are creating a database for sale to someone else it also NEEDS to be split. Its OK to not split it during development, but before you start user testing it needs to be split. And ESPECIALLY before it goes into production.

You may need to support or enhance it. Working with a split database makes it easy for you to work on it and then send the user a new front end so they can co9ntinue to use it and store their data.

[Micromax]

Thanks again Scott. I won't be supporting it. It sounds bad, but it will be sold as is. I hope If I split it and test it, that will be the final test. I would have to use a Delete Query and reset the autonumber fields back null. I have this Menu Manger Add on from a book I purchased "Access Inside Out 2002" I have to read the instructions about the .mda I'm still not decided if I will go that route. I hope splitting the database is easy on Access. I saw the code on Northwind where it uses a Public Function for forms. I'm not very Visual basi oriented and it's a hit and miss type of programming I'm doing with code that is available. I'm scared a little bit, but I hope this databsae works properly on other computers from Access 2002 and up. Why am I telling you this? You would be my go to guy, for a fee(your fee) if you wanted to review the database before I can distribute it. No obligations on your part. I know you know Access and VB . Better than myself.