Well after working with it nearly all day I can say that it did not completely FIX it but SOMETHING happened due to the behavior change of the word "Memo" versus "memo" that I mentioned.
I have something going on that's throwing the c0000005 error when VFP7 performs a read operation (specifically, SCAN REST; SCAT MEMV MEMO; other stuff; ENDS) and it's not being caught so it blows VFP7 oout of the water. Once I was hung on a record and it would blow up every time until I did a SCAT MEMV. I said the heck with the contents of that memo since it was probably trashed anyway and went on. I can process a few records before it blows up, then a few more, etc.
A
Previous
Next
Reply
View the map of this thread
View the map of this thread starting from this message only
View all messages of this thread
View all messages of this thread starting from this message only