Rx_
Nothing In Moderation
- Local time
- Today, 01:28
- Joined
- Oct 22, 2009
- Messages
- 2,803
This seems to be a requirement for Access 2013 over Access 2010. Going to mark this as solved unless someone else has input.
Thanks!
A release was made. The users were active and reported that it worked just great. After the users caught up using this, they went on to other projects.
Shortly thereafter a couple of weeks ago, the Access 2010 was upgraded to Access 2013.
After making some other changes to the form, it is customary to retry the Add, Edit and Delete on various task to insure nothing changed that wasn't suppose to have changed.
The following first line of code caused an error.
This is a Linked table to SQL Server using SQL Server Native Client 11.0
db.Execute "DELETE FROM tblDSU WHERE DSUID = " & lstDSUs.Value, dbFailOnError
db.Execute "DELETE FROM CommentsDSU WHERE DSUID = " & lstDSUs.Value, dbFailOnError
Changing both to:
db.Execute "DELETE FROM tblDSU WHERE DSUID = " & lstDSUs.Value, dbFailOnError + dbSeeChanges
it worked fine.
Granted, this delete was on a record with an Identity column.
However, a search shows there are dozens of statements like this.
Should all of these statements be bulk updated with the DBSeeChanges where there is a WHERE statement?
Thanks!
A release was made. The users were active and reported that it worked just great. After the users caught up using this, they went on to other projects.
Shortly thereafter a couple of weeks ago, the Access 2010 was upgraded to Access 2013.
After making some other changes to the form, it is customary to retry the Add, Edit and Delete on various task to insure nothing changed that wasn't suppose to have changed.
The following first line of code caused an error.
This is a Linked table to SQL Server using SQL Server Native Client 11.0
db.Execute "DELETE FROM tblDSU WHERE DSUID = " & lstDSUs.Value, dbFailOnError
db.Execute "DELETE FROM CommentsDSU WHERE DSUID = " & lstDSUs.Value, dbFailOnError
Changing both to:
db.Execute "DELETE FROM tblDSU WHERE DSUID = " & lstDSUs.Value, dbFailOnError + dbSeeChanges
it worked fine.
Granted, this delete was on a record with an Identity column.
However, a search shows there are dozens of statements like this.
Should all of these statements be bulk updated with the DBSeeChanges where there is a WHERE statement?
Last edited:
