While it will copy forms, queries, etc., it's not intended for that purpose.
As Cheval stated, you should only be replicating the data. Your application
should be split into a front-end, with only the back-end being replicated.

No problem, Access has some unwritten rules that makes the learning curve a
little steeper than expected.

Q1) You can keep the Design Master on your laptop. It makes no difference
where you keep it. So if you want to take it home, the laptop would be a
perfect place. Just remember not to move it with any tool other than the
Replication ones. One more bit of advice on that, I would recommend that you
create another replica on the server called [AppName}_backup.mdb or
something similar. The reason for this is that in the worse case of a
corruption between the Design Master and the server backend, you shouldn't
restore a backup from tape or what ever you use to backup your system. Also
create another replica on your laptop (see below) so that you have
App_DM.mdb and a App_Be.mdb.
Q2) Interesting problem when people first come across this, but it is easily
solved. Yes you are right, but don't make it hard for yourself.
   Part 1) From the users point of view their backend is on the server, so
their tables should be linked to say J:\App\App_Be.mdb. You on the other
hand link to your backend C:\Prog..files\App\App_Be.mdb. The way I solve
this is in two parts. In the front end replica, off the Autoexec macro, have
a function that in code searches for the C: backend, if not finding it looks
for the J: backend to link to and use table object method ".connect" to
relink the tables to either database it finds.
   Part 2) You want to makes changes to the front end and have the users
get the latest version. This is easy. Have the users run a VB Script (or
JScript whatever to open the app) which copies the app.mde file from the
server and then opens it. That way every time they open the application,
they get the latest version.
Q3) No, I may have not communicated that very well. Access _can_ replicate
everything, but it doesn't do it well, so you shouldn't. You always copy the
front end everywhere, but you replicate _only_ the backend.

Cheval,

Thank you, thank you, thank you.  This was excellent help (perhaps the
best I have ever received on a newsgroup)!!!

Would appreciate it if you could help me a little further...

1.  I am not using windows file copy to take the design master home.
No, my design master is located on my laptop and I am replicating to
the server.  Should I continue this or are you stating I should put the
design master on the server... I don't understand, please clarify.
2.  Once I split the db and replicate the tables to the server , how do
I manage changes to the front-end on the individual computers?  Do you
have articles that you could refer me to?...  for example, do I simply
delete the old front-end and copy the new front-end (on each
workstation)... then relink the front-end to the back-end??
3.  fyi... You stated that replication does not copy forms, queries,
etc but it certainly does copy forms.  I have checked the replicated db
after replication and confirm that the form designs have changed but
the code has not.  Perhaps an issue with Access 2003.
Thanks again for your help.

Art