J
JDWilk01
Hi,
I have an MS Access 2003 MDB with tables linked to a SQL Server 2005
database. The MDB has a parent form that has a subform that is linked via
parent/child. Both forms' record sources are linked tables to the SQL Server
database.
Some code issues a "DoCmd.GoToRecord acDataForm, ParentFormName, acNewRec"
command to create a new record on the parent form, then saves the record. I
find that a new record is created, but just sometimes the parent and child
form do not display the new record. Instead they display some other existing
record(s) in the database.
More code subsequently adds records to the subform, but those records are
linked to the existing (invalid) parent record instead of the new record.
This behavior does not occur consistently. Most of the time the code works
as expected. It seems to fail several times a day per user.
The problem started the day we upgraded the database to SQL Server 2005. It
had been working without a problem when linked to a SQL Server 2000 version
of the database.
Replication was set up in the SQL 2000 database version, and has been
recreated in the 2005 version of the database. Both replication topologies
include the tables in the form and subform.
For reference, this problem was reported through this Community by jrsmoots
on 6/30/2009 and responded to (at least provisionally) by Albert D. Kallal on
7/1/2009. Has there been a solution to this problem since then?
Any help on this would be greatly appreciated.
Many thanks,
I have an MS Access 2003 MDB with tables linked to a SQL Server 2005
database. The MDB has a parent form that has a subform that is linked via
parent/child. Both forms' record sources are linked tables to the SQL Server
database.
Some code issues a "DoCmd.GoToRecord acDataForm, ParentFormName, acNewRec"
command to create a new record on the parent form, then saves the record. I
find that a new record is created, but just sometimes the parent and child
form do not display the new record. Instead they display some other existing
record(s) in the database.
More code subsequently adds records to the subform, but those records are
linked to the existing (invalid) parent record instead of the new record.
This behavior does not occur consistently. Most of the time the code works
as expected. It seems to fail several times a day per user.
The problem started the day we upgraded the database to SQL Server 2005. It
had been working without a problem when linked to a SQL Server 2000 version
of the database.
Replication was set up in the SQL 2000 database version, and has been
recreated in the 2005 version of the database. Both replication topologies
include the tables in the form and subform.
For reference, this problem was reported through this Community by jrsmoots
on 6/30/2009 and responded to (at least provisionally) by Albert D. Kallal on
7/1/2009. Has there been a solution to this problem since then?
Any help on this would be greatly appreciated.
Many thanks,