Portable Front End

[jriano]

How to carry the db front end home

I have a front end for my db. I would like to be ablo to carry it home to work on some modifications. What is the right way of doing that without creating conflicts? i can even carry the db too. What I have done so far, is I would make modifications at home (to the front end), and then at the office I would just overwrite the old version on the server., But last week the vb got corrupted and I feel it was because of mine carrying and overwriting the front end. Could you guys tell me what can and can not be done in respect to this?
Thank you

 

[WayneRyan]

jriano,

You can take the "front end" home on a floppy, a zip, or even
a CD. Replacing it after modifications should not corrupt your
database.

Putting it on a CD will make it "Read Only" until you use windows
to change it back to "Read/Write". Your environment at home
should use the same linking configuration as your environment
at work.

Wayne

 

[ghudson]

You should not have any problems carrying the front end home to work on it and then replace it over the front end at work. I prefer to copy my db's to a USB thumbnail drive so that I can work on the front end and back end on the thumbnail drive. That prevents to hassle of burning the files to a CD. You just have to relink the tables when you move the front end and back end around no matter how you move the db's.

Making backup copies is always recommended, no matter what or when you are modifying the db.

Also, do you have the same version of Access at home and at work?

HTH

 

[jriano]

yes, I have the same acces version. Ok, so I have done it the right way, I dont know then why some of my vb got corrupted. lets hope it does not happen again. Thank you

 

[Kevin_S]

I dont know then why some of my vb got corrupted. lets hope it does not happen again.

Did you try compiling the code in the debug menu? Seems odd that vba would just "become" corrupted (data yes but vba ???) it might have been something that had an error before you copied the updated FE over the previous version.... Also - try repair and compacting the db...

HTH,
Kev