Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Chris Miller on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Creating Batch file to import / copy Access

Status
Not open for further replies.

Steven547

Technical User
Sep 15, 2004
165
US
Need a little help please. I have an Access DB that is on a shared network folder (example: M:\Folder1\Folder2\MyAccessDB)

The users have to copy it to their desktop to use it. But, some users aren't very computer literate so I don't want to go to each and every desk and copy it for them. I want to have a file that when double clicked, copies the DB to their Desktop. I remember seeing this done, just don't remember how it is written in notebad to create a batch file to do this. Can someone please remind me how that is done?

Also, is it possible that one they have the DB on their desktop, and I make changes to the FORM, then can just copy the form over instead of the entire DB (erasing their data in the process). Is there a batch file to do that as well?

Thank you for you help.

 
It seems that you do not have a split FE/BE set-up. This is not recommended. Data (tables) should be stored on the server (BE) and the users should have a copy (FE) with forms, reports, some queries and all coding. When a form or such like is changed, the user should get a copy of the new front-end (FE). It is likely that data will be common to several users, so it should be stored centrally. It is unsafe to have a batch file that will copy a database unless you have this type of set-up because at some stage a user will overwrite their data and get upset.

You may wish to read:
Then:
 
Thanks.

In reference to the FE/BE...currently, not everyone has user rights to all the folders. Would I need to
1: have a folder created that grants all users read/write access.
2: When I split the database, the BE is stored in this folder (along with a copy of the FE), but the FE also goes to their computer. Right?
3: And then follow the logic you mentioned about copying just the FE to their computers.

Reason why I was just copying the entire DB, is because some users get the "Recordset can not be saved..." error, after I split the DB (and they have a copy of the FE on their desktop) which I believe is a user rights (access to the folder read/write) issue. Would those assumptions and "procedures" be correct then?

Thanks.
 
The folder you create will also need delete permissions because of the lock file (ldb). Otherwise, the above should suit. Post back if you have any problems.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top