|
-
Feb 6th, 2002, 03:47 AM
#1
Thread Starter
New Member
Application hangs in XP
I have a program which runs some calculations, then writes to a grid for viewing and also stores that info into an Access database.
It works fine in my 133 mhz machine in Win 95, 98 and 2000, but hangs in my 1.1 ghz machine in XP.
When I trap it via breakpoints it works fine in XP. I've even eliminated pieces of code trying to find the error. No luck. Individually, it doesn't error, until I put all code all back in collectively
My guess is that the database is still committing records before the next piece of code comes along causing the problem. I've a label which is supposed to refresh. It does hit that command, but never refreshes. It appears aribtrary. In other words, sometimes a group of records fails to commit, and then another time it is a differnet group of records which fails, and the earlier one which failed successfully commits.
My question is how can one be sure the database record has successfully committed before executing the next line of code? And any ideas?
Thanks
Losing It!
-
Feb 6th, 2002, 05:05 AM
#2
it depends on the code you are using to write to the database (there are far too many database access methods to generalise), post it and i'll have a look...
-
Feb 6th, 2002, 07:47 AM
#3
Fanatic Member
Look at with events.
These fire off when things are done to a database.
You just get these to write to file and view the file after to see what happened and also add time stamps so you can check the time it took to process records.
Gary Lowe 
VB6 (Enterprise) SP5
ADO 2.6
SQL Server 7 SP3
OK I know my spelling and grammer is crap so don't quote me on it!
To err is human to take the P! is only natural !!
Click on the top section of image for Marcus Miller website and bottom section of image for 'Run For Cover' sound clip

Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules
|
Click Here to Expand Forum to Full Width
|