General information
Category:
Coding, syntax & commands
Barbara -
Well, that's comforting . I'm just grateful there are people like you around who have 'been there, done that' for people like me who are just starting to use VFP. Thanks again.
Sylvia
>>I went back and looked at my SELECT statement, which as I mentioned was followed by an Append blank. But following that was a line with a syntax error (I'd used a table.field = table2.field2 instead of replace), so when I fixed that, the error went away. I appreciate you help. Do you have any explanation on why this kind of error (in my case 2 lines down) would cause VFP to report an error on the SELECT line?
>>
>>Sylvia
>
>Sylvia, sorry for the delay. No, I don't have any explanation, but I've seen it happen before. Error systems are notoriously unreliable. They give the best message they can, but it isn't always right. On one system I'm working on, the message on the screen is almost always different from the logged form/method/line position. We haven't tracked down the problem (it's internal to the commercial framework) so we tell the users to just exit gracefully and we'll read the errorlog when they call us. Not pretty, but they're actually happy not to be responsible for looking at the messages.
Previous
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