Front End and Back End

[Linda \(RQ\)]

Hi Everyone,
This is the first time I have made a database and split it. Using Access
2003. I created my database on my home computer. I split it and moved it
to the network drive at work. Now I have a copy both at home and work. My
question is, can I work on the front end at home which is linked to the
original back end at home then move the front end to work and relink to the
back end there? The back end there will have more and up to date records as
we continue to edit and add new records. Will it mess things up if I use
two different back ends when adding objects other than tables? I may work
on the front end at work some times, then will send it home to replace the
front end I have here and vice versa. What's the best way to do this? Keep
in mind I'm a beginner.


Thanks,
Linda

 

[Guest]

Linda,

That's the beauty of splitting your db, you can take the front-end and work
on it independently and then later place it on the server update the links to
the back-end and your in business! Creating new objects isn't really an
issue either. Even tables. You can create new objects and then if it is a
table, import into the back-end when you get back at work, as for the other
elements they are supposed to be part of the front-end anyway so no problenm
there.

Do make sure however that you always have they latest mdw file for your db
wherever you are working because it can get messy if you used on old version
which didn't have all the users... Then you will have to manually make
adjustment.

Your are on the right track! You will no doubt settle into a routine that
works for your needs.

Daniel

 

[Linda RQ]

Thanks, Daniel.

I don't have an mdw. I think that is the security part...You can just
forget that right now. <g> I am in deep enough for a little while.

Linda