copy form from one db to another

[memilanuk]

Hello,

I'm working on a database based on a copy that I keep with me on a usb drive. I'm doing the design and layout work, mostly making changes to the forms and reports at this point. The end user has the actual working copy and is updating records in it, etc. - the copy I have is slightly older (in terms of records) but has newer forms.

If I want to update the forms, reports, etc. on the end-user working copy, I should be able to sit down at that computer, open up both copies, and copy over the new forms to the working copy and then everything should work normally, correct? I plan on making backups on both sides before hand, but I'd rather avoid un-necessary complications if possible.

Thanks,

Mont

 

[boblarson]

The database should be split into a frontend and backend (tables only) and that way you can just replace their frontend with the latest version.

 

[memilanuk]

Hello Bob,

Thanks for the response. Would that be the best solution considering I have to go over to the other person's house (volunteer organization) to update the database anyways? I've seen stuff about splitting the database before, but I'd always assumed it was just for multi-user access while this is strictly one-user-at-a-time. If it would make it so I could just email them a new front-end rather than having to synchronize our schedules to meet, that would be a worthwhile improvement.

Thanks,

Monte

 

[boblarson]

Well, you would need to relink, but if you implemented some relink code (free from Access MVP Armen Stein) then you could just send them the new frontend and it would work. The only time you'd need to deal with the backend is if tables had changes or you had new tables.

 

[memilanuk]

Well, that probably would be just the ticket for the future... but having about zero VBA knowledge at this point and I was planning on swinging by his place tomorrow afternoon to copy the forms over... the 'correct' solution may have to wait a bit

 

[boblarson]

You can use the Export function to export from your version to the other version. I would do it manually at this point but I would also make sure that Name Auto Correct is turned off in both databases and then do the export. If you export something with the same name it will append a 1 on to the end then you can go in and delete the old ones and rename without the 1 and everything should work okay.

Another reason for using Export (or Import from the other) is that it will usually take care of any corruption that might be starting to appear. If you just copy and paste, it will not.