how ca i do this?

[Guest]

I have an access 2000 database located on the server which will give return a
parts list and how many parts we have in stock for the devices the operator
has selected. I have a similar program on a workstation with the needed
tables linked and other objects imported. What I am trying to do is to be
able to run the program on the desktop so that it'll return all the parts
needed for the selected devices and also list the other devices that use the
same parts from the server program. I am able to get a query to return the
parts that match in both databases but I can't seem to figure out how to
return all the parts that I need at the workstation database

Thank you

 

[Douglas J. Steele]

Whatever generates the list on the server should work on the workstation as
well. There's no difference in terms of capabilities between a database with
the tables in it, or a database with the tables linked to another database.
It's not as though the database on the server is actually running on the
server: the client machine runs the Access program, not the server machine.

Perhaps you can explain a little more about what you mean by "a query to
return the parts that match in both database", since if you're linked to
another database, the data should be identical.

 

[Guest]

The databases are basiclly identical, the only difference being the naming
convention used so that I could tell them apart. The purchasing department
uses the server database and I (or my boss) uses the workstation database so
that we don't corrupt their numbers. What I mean "a query..." is there are
devices that will use some of the same parts as other devices. I am trying
to be able to see all of the parts needed that I input on the workstation
database as well as the the shared parts and what devices they are used on
from the server database

 

[Guest]

here's kind of what I'm looking for

Device A uses parts 1,2,3,4,5

Device B uses parts 1,2,5,6,7

I would like to have this returned to me via query:

Device A parts:
1 device b
2 device b
3
4
5 device b

 

[Douglas J. Steele]

Sorry, without more details about the tables involved (and where each
exists), it's really not possible to offer any suggestions.

It almost sounds to me as though the two different databases are for the two
different devices. That's seldom a good idea. Have 1 database that contains
all of the data, and have everyone query the same database. (From a
deployment perspective, you'd split the database into a front-end,
containing the queries, forms, reports, macros and modules, and a back-end,
containing the tables and relationships. Only the back-end would be placed
on the server. Each user would have his/her own copy of the front-end,
preferably on their hard drive.)

 

[Joseph Meehan]

The databases are basiclly identical, the only difference being the
naming convention used so that I could tell them apart. The
purchasing department uses the server database and I (or my boss)
uses the workstation database so that we don't corrupt their numbers.
What I mean "a query..." is there are devices that will use some of
the same parts as other devices. I am trying to be able to see all
of the parts needed that I input on the workstation database as well
as the the shared parts and what devices they are used on from the

It really sounds to me like you should have only one database. The
users all can have their own database linked to the one main database
(called a back end) on a server. They can each have their own forms,
reports etc and with user level security be limited to what they can access
or change.