Can't Update Records

[SeniorTrans]

Hi,

I've now put both tables in the same database...not linked... I have joined
the two tables with a one-to-one join. Have built a form and use that query
as the underlying Recordsource. But it will not let me update the record.
when I try to edit...I get a warning that someone else has edited the record
and saved it before I did and therefore my changes won't be saved...and I'm
supposed to try again.

What am I doing wrong? I've made hundreds of forms this way with no
problem.

Help Please.

JP

 

[John Vinson]

Hi,

I've now put both tables in the same database

You're apparently assuming either that you are the only person asking
questions here, or that all the volunteers have perfect memories and
remember your post from however long ago. Neither assumption is valid!
Which "two tables"?

...not linked... I have joined
the two tables with a one-to-one join.

One to one relationships are VERY VERY RARE. If you're not familiar
with the term "subclassing", then you probably don't want a one to one
relationship. One to many is MUCH more likely.

Have built a form and use that query
as the underlying Recordsource. But it will not let me update the record.
when I try to edit...I get a warning that someone else has edited the record
and saved it before I did and therefore my changes won't be saved...and I'm
supposed to try again.

What am I doing wrong? I've made hundreds of forms this way with no
problem.

If you'ld care to post the SQL of the query, with a description of the
tables; and indicate what the Primary Key of each table is, and how
they are related, perhaps someone could help. Generally you might do
better to use a Form for the "master" table with a Subform for the
related table rather than creating a query to update both.

 

[Bikerman]

One to one relationships are VERY VERY RARE. If you're not familiar
with the term "subclassing", then you probably don't want a one to one
relationship. One to many is MUCH more likely.

John,
Question here, I have many tables that are one to one relationships. I am new to this so I am asking to see if I am doing something wrong. My tables have to do with different medical terminologies that apply to a specific client (patient).
For instance I have a table with all the information for that client, name address, tel number etc. Then I created one to one relationships with tables that describe this particular clients mental status (about twenty or so fields).
The only way to link them is through the SS#, so this is what I make as the linkfield with no duplicates allowed since the client can only have one set of these descriptions. Is this one of the times when a one to one relationship would be "normal" for lack of a better word?
Bikerman

 

[John Vinson]

John,
Question here, I have many tables that are one to one relationships. I am new to this so I am asking to see if I am doing something wrong.

Without seeing the database I can't be sure, but my guess is that you
are.

My tables have to do with different medical terminologies that apply to a specific client (patient).

Sounds like a Many to Many relationship: each Patient has many
applicable Terminologies; each Terminology applies to many Patients.
Right?

For instance I have a table with all the information for that client, name address, tel number etc. Then I created one to one relationships with tables that describe this particular clients mental status (about twenty or so fields).

Sounds like you're storing mental-status data in fieldnames - always a
Bad Idea.

The only way to link them is through the SS#, so this is what I make as the linkfield with no duplicates allowed since the client can only have one set of these descriptions. Is this one of the times when a one to one relationship would be "normal" for lack of a better word?
Bikerman

No, it is not, if I understand it correctly. Instead, consider three
tables:

Patients
PatientID
LastName
FirstName
<other bio data>

Conditions
ConditionID (perhaps an ICD-9 code, some unique identifier)
Condition <text>
<other info about this condition in general>

Symptoms
PatientID <many side foreign key to Patients>
ConditionID <many side foreign key to Conditions>
Comments
<other fields concerning this patient/this condition, e.g. severity>

 

[John Vinson]

Thanks John,
Perhaps you can take a look at it?
my email is (e-mail address removed)
I would greatly appreciate it!!
Bikerman

I'd be willing to do so, but only at my current consulting rates. I'm
a self-employed database design consultant, volunteering my time on
the newsgroups; downloading and editing a database goes beyond what I
have time to do on that basis. Email me at jvinson <at> WysardOfInfo
<dot> com if you would like a copy of my consulting terms.

Hope you understand my position!

Posted and emailed. Note that posting your email address in clear in
the newsgroups is risky - viruses and spammers regularly harvest them.
:-{(