I urge you to re-think your data design. Access is a relational database,
and you will get the best use from it by designing normalized tables.
This means ONE table, not 7. If you add a single field to designate which
laptop/field rep/whatever "owns" the row, you could put all the data in one
table.
Good luck
Jeff Boyce
<Access MVP>
That is a good idea...I did not realize I could do that, it would make it
alot easier to work with..
...currently the master table includes all customer data and the field rep
table (which they enter shipping, installation and completion dates and other
misc info) is linked by job number...
...I was originally going to put in an additional field for Field rep
assignment...can I do that and assign ownership to the line through that
field or am I going to have to recreate the table?
Also, would I then still use the replication method of updating the data base?
Thanks,
Tonkle
> I urge you to re-think your data design. Access is a relational database,
> and you will get the best use from it by designing normalized tables.
[quoted text clipped - 56 lines]
> > > > Thanks,
> > > > tonkle
Jeff Boyce - 30 Jun 2005 12:58 GMT
You can add a field to a table and use an update query to change the value
in that new field.
If you have a master database, and want to "merge" changes into it, take a
look into replication.
Good luck
Jeff Boyce
<Access MVP>
> That is a good idea...I did not realize I could do that, it would make it
> alot easier to work with..
[quoted text clipped - 70 lines]
> > > > > Thanks,
> > > > > tonkle
Tonkle - 30 Jun 2005 22:53 GMT
Thanks Jeff for everything!
Tonkle
> You can add a field to a table and use an update query to change the value
> in that new field.
[quoted text clipped - 96 lines]
> > > > > > Thanks,
> > > > > > tonkle