Access 97 bound form edits the previous record, not the one displayed.

[Steve Strik]

My Problem:

I have created a database here at work that is exhibiting some very
strange behaviour.

Essentially the database is structured in a manner where one table is
a master record table (tbl_MainRegister) providing a unique identifier
for documents and a means for identifying the docuement type. There
are then 4 additional tables (tbl_Meetings, tbl_Documents,
tbl_Project, tbl_Correspondence) which store the document details.
There is one form for each table and the docuement detail forms are
bound forms.

The problem I am having is where a record is selected on the main form
(details are in tbl_document) and then edited in the bound form, on
returning to the main form the previous document of that specific type
is displayed. When the user returns to the docuement form he finds
that the system edited the previous record and not the record
displayed in the form. This was only occuring on a switch back to the
main form using the button provided.

Now this problem is occuring when the user selects the previous record
navigation button on the form. I have been unable to replicate this
problem consistently as it works as intended on my machine and on
several others.

How can I fix this?

Regards
Steve

[Allen Browne]

More information, please Steve.

What version of Access/Office, and what service pack? (See Help | About.)

Open the main form in design view. What is in its RecordSource property?

Still in design view, right-click the edge of the subform control to get its
properties.
What is in the:
LinkMasterFields?
LinkChildFields?
Which tables do these fields come from?
Are they primary key fields? Of which table?
Or foreign key fields?

From your explanation, there is a one-to-many relationship between
tbl_MainRegister and tblDocuments. If the main form were bound to
tbl_MainRegister and its primary key was MainRegisterID, then that would
normally be the field in the LinkMasterFields. tblDocuments would have
MainRegisterID as a foreign key, and that would be the field in the
LinkChildFields. Is that what you have?

--
Allen Browne - Microsoft MVP. Perth, Western Australia.
Tips for Access users - http://allenbrowne.com/tips.html
Reply to group, rather than allenbrowne at mvps dot org.

"Steve Strik" <st********@hotmail.com> wrote in message
news:2e**************************@posting.google.c om...

My Problem:

I have created a database here at work that is exhibiting some very
strange behaviour.

Essentially the database is structured in a manner where one table is
a master record table (tbl_MainRegister) providing a unique identifier
for documents and a means for identifying the docuement type. There
are then 4 additional tables (tbl_Meetings, tbl_Documents,
tbl_Project, tbl_Correspondence) which store the document details.
There is one form for each table and the docuement detail forms are
bound forms.

The problem I am having is where a record is selected on the main form
(details are in tbl_document) and then edited in the bound form, on
returning to the main form the previous document of that specific type
is displayed. When the user returns to the docuement form he finds
that the system edited the previous record and not the record
displayed in the form. This was only occuring on a switch back to the
main form using the button provided.

Now this problem is occuring when the user selects the previous record
navigation button on the form. I have been unable to replicate this
problem consistently as it works as intended on my machine and on
several others.

How can I fix this?

Regards
Steve

[Steve Strik]

Thanks for your reply Allen.

There are no subforms in use in this database. I'm using code to open
the forms when the user clicks a button.

We are using Office 97 on NT4SP6a and on my machine (I don't have
problems. The database works perfectly) Access is SR1.

There is a one to one relation ship between tbl_MainRegister and
tbl_Documents.

When a new record is created in the main register form I use code to
create a record in the correct table dependant on the document type.

I'll email the code to you for the two forms as it is quite long.

This problem is only occurring repeatably on one machine (a laptop).
I can't see anything in my code that can cause it as the Docuemnts
form is just a bound form.

Regards
Steve
"Allen Browne" <Al*********@SeeSig.Invalid> wrote in message news:<40***********************@freenews.iinet.net .au>...

More information, please Steve.

What version of Access/Office, and what service pack? (See Help | About.)

Open the main form in design view. What is in its RecordSource property?

Still in design view, right-click the edge of the subform control to get its
properties.
What is in the:
LinkMasterFields?
LinkChildFields?
Which tables do these fields come from?
Are they primary key fields? Of which table?
Or foreign key fields?

From your explanation, there is a one-to-many relationship between
tbl_MainRegister and tblDocuments. If the main form were bound to
tbl_MainRegister and its primary key was MainRegisterID, then that would
normally be the field in the LinkMasterFields. tblDocuments would have
MainRegisterID as a foreign key, and that would be the field in the
LinkChildFields. Is that what you have?

--
Allen Browne - Microsoft MVP. Perth, Western Australia.
Tips for Access users - http://allenbrowne.com/tips.html
Reply to group, rather than allenbrowne at mvps dot org.

"Steve Strik" <st********@hotmail.com> wrote in message
news:2e**************************@posting.google.c om...

My Problem:

I have created a database here at work that is exhibiting some very
strange behaviour.

Essentially the database is structured in a manner where one table is
a master record table (tbl_MainRegister) providing a unique identifier
for documents and a means for identifying the docuement type. There
are then 4 additional tables (tbl_Meetings, tbl_Documents,
tbl_Project, tbl_Correspondence) which store the document details.
There is one form for each table and the docuement detail forms are
bound forms.

The problem I am having is where a record is selected on the main form
(details are in tbl_document) and then edited in the bound form, on
returning to the main form the previous document of that specific type
is displayed. When the user returns to the docuement form he finds
that the system edited the previous record and not the record
displayed in the form. This was only occuring on a switch back to the
main form using the button provided.

Now this problem is occuring when the user selects the previous record
navigation button on the form. I have been unable to replicate this
problem consistently as it works as intended on my machine and on
several others.

How can I fix this?

Regards
Steve

[Allen Browne]

Please do not email direct.

First thing to do would be to apply Service Release 2 for Access 97 to the
problem machine.

--
Allen Browne - Microsoft MVP. Perth, Western Australia.
Tips for Access users - http://allenbrowne.com/tips.html
Reply to group, rather than allenbrowne at mvps dot org.

"Steve Strik" <st********@hotmail.com> wrote in message
news:2e**************************@posting.google.c om...

Thanks for your reply Allen.

There are no subforms in use in this database. I'm using code to open
the forms when the user clicks a button.

We are using Office 97 on NT4SP6a and on my machine (I don't have
problems. The database works perfectly) Access is SR1.

There is a one to one relation ship between tbl_MainRegister and
tbl_Documents.

When a new record is created in the main register form I use code to
create a record in the correct table dependant on the document type.

I'll email the code to you for the two forms as it is quite long.

This problem is only occurring repeatably on one machine (a laptop).
I can't see anything in my code that can cause it as the Docuemnts
form is just a bound form.

Regards
Steve
"Allen Browne" <Al*********@SeeSig.Invalid> wrote in message

news:<40***********************@freenews.iinet.net .au>...

More information, please Steve.

What version of Access/Office, and what service pack? (See Help | About.)
Open the main form in design view. What is in its RecordSource property?

Still in design view, right-click the edge of the subform control to get its properties.
What is in the:
LinkMasterFields?
LinkChildFields?
Which tables do these fields come from?
Are they primary key fields? Of which table?
Or foreign key fields?

From your explanation, there is a one-to-many relationship between
tbl_MainRegister and tblDocuments. If the main form were bound to
tbl_MainRegister and its primary key was MainRegisterID, then that would
normally be the field in the LinkMasterFields. tblDocuments would have
MainRegisterID as a foreign key, and that would be the field in the
LinkChildFields. Is that what you have?
"Steve Strik" <st********@hotmail.com> wrote in message
news:2e**************************@posting.google.c om...

My Problem:

I have created a database here at work that is exhibiting some very
strange behaviour.

Essentially the database is structured in a manner where one table is
a master record table (tbl_MainRegister) providing a unique identifier
for documents and a means for identifying the docuement type. There
are then 4 additional tables (tbl_Meetings, tbl_Documents,
tbl_Project, tbl_Correspondence) which store the document details.
There is one form for each table and the docuement detail forms are
bound forms.

The problem I am having is where a record is selected on the main form
(details are in tbl_document) and then edited in the bound form, on
returning to the main form the previous document of that specific type
is displayed. When the user returns to the docuement form he finds
that the system edited the previous record and not the record
displayed in the form. This was only occuring on a switch back to the
main form using the button provided.

Now this problem is occuring when the user selects the previous record
navigation button on the form. I have been unable to replicate this
problem consistently as it works as intended on my machine and on
several others.

How can I fix this?

Regards
Steve

[Steve Strik]

No chance of doing that. If the IT people did that it might be seen
as costomer service and we can't let that happen or it might become an
expected behaviour :)

Sorry for the direct emails.

The problem is definitly only effecting one machine (a laptop, the
only user of course) and he will just have to log onto a different
machine for updating his data if it is a problem within access itself.

Thanks Allen.

Regards
Steve

"Allen Browne" <Al*********@SeeSig.Invalid> wrote in message news:<40***********************@freenews.iinet.net .au>...

Please do not email direct.

First thing to do would be to apply Service Release 2 for Access 97 to the
problem machine.

--
Allen Browne - Microsoft MVP. Perth, Western Australia.
Tips for Access users - http://allenbrowne.com/tips.html
Reply to group, rather than allenbrowne at mvps dot org.

"Steve Strik" <st********@hotmail.com> wrote in message
news:2e**************************@posting.google.c om...

Thanks for your reply Allen.

There are no subforms in use in this database. I'm using code to open
the forms when the user clicks a button.

We are using Office 97 on NT4SP6a and on my machine (I don't have
problems. The database works perfectly) Access is SR1.

There is a one to one relation ship between tbl_MainRegister and
tbl_Documents.

When a new record is created in the main register form I use code to
create a record in the correct table dependant on the document type.

I'll email the code to you for the two forms as it is quite long.

This problem is only occurring repeatably on one machine (a laptop).
I can't see anything in my code that can cause it as the Docuemnts
form is just a bound form.

Regards
Steve
"Allen Browne" <Al*********@SeeSig.Invalid> wrote in message

news:<40***********************@freenews.iinet.net .au>...

More information, please Steve.

What version of Access/Office, and what service pack? (See Help | About.)
Open the main form in design view. What is in its RecordSource property?

Still in design view, right-click the edge of the subform control to get its properties.
What is in the:
LinkMasterFields?
LinkChildFields?
Which tables do these fields come from?
Are they primary key fields? Of which table?
Or foreign key fields?

From your explanation, there is a one-to-many relationship between
tbl_MainRegister and tblDocuments. If the main form were bound to
tbl_MainRegister and its primary key was MainRegisterID, then that would
normally be the field in the LinkMasterFields. tblDocuments would have
MainRegisterID as a foreign key, and that would be the field in the
LinkChildFields. Is that what you have?
"Steve Strik" <st********@hotmail.com> wrote in message
news:2e**************************@posting.google.c om...
> My Problem:
>
> I have created a database here at work that is exhibiting some very
> strange behaviour.
>
> Essentially the database is structured in a manner where one table is
> a master record table (tbl_MainRegister) providing a unique identifier
> for documents and a means for identifying the docuement type. There
> are then 4 additional tables (tbl_Meetings, tbl_Documents,
> tbl_Project, tbl_Correspondence) which store the document details.
> There is one form for each table and the docuement detail forms are
> bound forms.
>
> The problem I am having is where a record is selected on the main form
> (details are in tbl_document) and then edited in the bound form, on
> returning to the main form the previous document of that specific type
> is displayed. When the user returns to the docuement form he finds
> that the system edited the previous record and not the record
> displayed in the form. This was only occuring on a switch back to the
> main form using the button provided.
>
> Now this problem is occuring when the user selects the previous record
> navigation button on the form. I have been unable to replicate this
> problem consistently as it works as intended on my machine and on
> several others.
>
> How can I fix this?
>
> Regards
>
>
> Steve

[Allen Browne]

If your IT department does NOT want to apply A97 SR2 to that computer, it is
in danger of destroying the reliability of the data anyway.

Without that service patch, the computer is likely to show one record on
screen, but actually write any updates over the top of a *different* record.
Details:
http://allenbrowne.com/bug-04.html

--
Allen Browne - Microsoft MVP. Perth, Western Australia.
Tips for Access users - http://allenbrowne.com/tips.html
Reply to group, rather than allenbrowne at mvps dot org.

"Steve Strik" <st********@hotmail.com> wrote in message
news:2e**************************@posting.google.c om...

No chance of doing that. If the IT people did that it might be seen
as costomer service and we can't let that happen or it might become an
expected behaviour :)

Sorry for the direct emails.

The problem is definitly only effecting one machine (a laptop, the
only user of course) and he will just have to log onto a different
machine for updating his data if it is a problem within access itself.

Thanks Allen.

"Allen Browne" <Al*********@SeeSig.Invalid> wrote in message

news:<40***********************@freenews.iinet.net .au>...

Please do not email direct.

First thing to do would be to apply Service Release 2 for Access 97 to the problem machine.