DWUTKA at marlow.com
DWUTKA at marlow.com
Wed Apr 12 10:01:00 CDT 2006
That can sometimes be a commit issue. Had a project a few weeks ago that was supposed to update a particular table when criteria were met. That update process was in it's own function, which had a few derived SQL statements, and it used CurrentProject.Connection.Execute strSQL to run them. In debug, stepping through, worked fine. In process though, it just didn't run. Switched it to DoCmd.RunSQL strSQL, worked like a charm. What I think happened is that I had the connection object tied up elsewhere, stepping through gave things time to commit, but running it straight didn't, so things were run, but the transactions were dropped. Drew -----Original Message----- From: Kim Wiggins [mailto:kimjwiggins at yahoo.com] Sent: Tuesday, April 11, 2006 9:10 PM To: accessd at databaseadvisors.com Subject: [AccessD] Access problem with tables Can someone please help me with this problem? I know it's something simple but I am not an Access database expert but I am learning everything I can. I follow your email list because I have learned a lot just by reading what the problems everyone has. I have three Access tables that update using VB code. When I click the Save button, they all save at the same time. All three tables (table A, B and C) each have 2 columns (columns 1 and 2) that are identical. When it saves, it is adding a new record to columns 1 and 2 in all three tables. The problem is, sometimes it saves to all three of the tables just fine and other times it may just save to 2 or 1 of them instead of all three. What would cause it to do that? What would cause such inconsistency to occur when it is using the same code every time? Thanks Kim Wiggins --------------------------------- How low will we go? Check out Yahoo! Messenger's low PC-to-Phone call rates. -- AccessD mailing list AccessD at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/accessd Website: http://www.databaseadvisors.com