relationships

[Maureen]

HELP!

I have an access 02 database, split frontend/backend
(backend is tables only) being run on an NT 2000 server
in a multiuser environemnt.

I have a company table, where all companies are stored
with a unique COMPID value, set to be the primary key;
indexed, no duplicates

I have an Inquiry Table, where all inquiries are stored
with a unique INQID value, set to be the primary key,
indexed, no duplicates.

When A company makes an inquriy - it gets recorded
through a form - which has the Inquiry table as it's
record source (through a query that sorts the records).
The company making the inquiry is recorded using the
COMPID code only - The query shows the COMPID code from
the INQUIRY TABLE - which is joined to the Company table
so all of the details about the company can be viewed on
the Inquriy form.

I have set up a one to many relationship (CompID Comapny
Table to CompID in the Inquiry Table) and enforced
referential integrity. So no inquiry can only belong to
an existing company - no inquiries to companyies that do
not exist (or so I thought).

I just found an instance where two users were inputting
companies and inquiries - something got screwed up and
the inquiry generated belongs to a companyID that does
not exist. It belongs to a company that one user was
trying to create at the same time but the company record
did not get saved - I have since modified the form to
SAVE RECORD once a company name has been typed in so I
believe that will improve this situation - BUT HOW DO I
HAVE AN INQUIRY BELONGING TO A COMPANY ID THAT DOES NOT
EXIST???

 

[Jeff Boyce]

Maureen

Are both front-end and back-end on the NT 2000 server?

 

[Maureen]

-----Original Message-----
Maureen

Are both front-end and back-end on the NT 2000 server?

--
More info, please ...

Jeff Boyce
<Access MVP>
.
Hi Jeff,

Thanks in advance for your help.

Both the FrontEnd and The BackEnd are on the server -
HOWEVER< the FrontEnd is also installed on the local PCs
of the multiple users - the users are supposed to use the
local frontend which links to the single backend on the
server.

I believe I had one user on the server's frontend and one
user on his local copy at the time data got mixed up and
an inquiry was generated with a CompID value that does
NOT belong to a current company.

 

[Jeff Boyce]

Maureen

Given the likelihood of corruption if more than one user "hits" the same
front-end (located on the server), the generally-accepted practice is to
never put the front-end on the server.

Distribute a "local" copy of the front-end to each PC/workstation.