okay so I'm on this mission to totally eliminate I/Os and Access Violation
errors from my app. I've changed code to create temp data before calling a
form or report that uses them, dropping temp tables prior to creating them, and
limiting the use of cursors. I'm not sure why but cursors seem to be the
source of most of these, anyone know why that would be (oh and I have checked
and re checked to make sure all vars are clearly defined prior to creating the
cursor)? As a result my users have had no errors since last Thursday; as in
the words of the great philosopher Homer Simpson, 'Wooo Hooo'.
Also just wondering where and what resources are used when the following set up
is done.
compiled exe and dlls on user workstation pointing to DB files on a server
processing a stored proceedure - is it the server where the DB is or is it
pulled over to the user workstation?
----- Original Message -----
From: Dennis McGrath
To: RBASE-L Mailing List
Sent: Friday, January 29, 2010 1:41 PM
Subject: [RBASE-L] - I/O error redux
I came across one place in my code which documented the problem I was having
wit temp tables.
I was inserting into an existing temp table.
The data came from a view and I was doing a group by on the selected data
coming out of the view
I frequently would get I/O errors, but not all the time.
So, I projected an empty temp table from the target table.
Then, I did the insert to the fresh new table.
Then, I appended the new table to the target table.
I haven't had the problem since.
I hope this help someone eliminate at lease some errors.
Dennis McGrath
