Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
Home
Discussion GroupsFormsForms ProgrammingQueriesModules / DAO / VBAReports / PrintingMacrosDatabase DesignSecurityConversionImporting / LinkingSQL Server / ADPMultiuser / NetworkingReplicationSetup / ConfigurationDeveloper ToolkitsActiveX ControlsNew UsersGeneral 1General 2
Access DirectoryToolsTutorialsUser Groups
Related Topics
SQL ServerOther DB ProductsMS OfficeMore Topics ...

MS Access Forum / Database Design / June 2005

Tip: Looking for answers? Try searching our database.

Looking for best solution

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
Tonkle - 28 Jun 2005 12:23 GMT
Hello,

I need to determine the best way to take a database in Access 2000 and
enable 7 field operaters to update infomation in the field and then have
their updates entered into the master database in the office.

The database has a master table with customer data and each field operator
would update relevant information in a secondary table linked to the master.  
By allowing them to update in the field on their laptops they would only need
to do some type of syncing with the master database.  This sync would update
the master database and then give them an updated copy of the master table.

They need to be able to view the master table information but only adjust
the information in the secondary table.  The master database table is
adjusted and added to throught the day by the office staff.

I am not sure the best course to take: FE/BE model in Access 2000,
Import/Export, or multiple databases linked to the master database

Thanks,
tonkle
Jeff Boyce - 28 Jun 2005 12:46 GMT
If you are saying that there's a chance the 7 could each/all modify the same
record (and even if there's no chance), take a look at "replication" (check
in the replication newsgroup, too).

Signature

Good luck

Jeff Boyce
<Access MVP>

> Hello,
>
[quoted text clipped - 17 lines]
> Thanks,
> tonkle
Tonkle - 29 Jun 2005 05:06 GMT
Thanks Jeff for your response,

I want each of the 7 laptops to only have access to change the data relevant
to them  (ie their own table) which should not be accessable to anyone else
unless they were accessing the master in the office.  Each of the 7 will
haver their own table to keep them from accessing someone else's data.

I will look at the replication newsgroup if you think that might be the best
solution...

> If you are saying that there's a chance the 7 could each/all modify the same
> record (and even if there's no chance), take a look at "replication" (check
[quoted text clipped - 25 lines]
> > Thanks,
> > tonkle
Jeff Boyce - 30 Jun 2005 01:36 GMT
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>

> Thanks Jeff for your response,
>
[quoted text clipped - 35 lines]
> > > Thanks,
> > > tonkle
Tonkle - 30 Jun 2005 05:11 GMT
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
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2008 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.