>One of my guys had this today (he had it about six weeks ago too). The line of code which 'fell over' was incrementing a form property by one - it has worked fine before.
>
>What he did was to retype the line and then delete the offending code. It seemed to work - may be a coincidence though!
This one fails only as Foxpro runtime is closed down on one app only, which uses an ActiveX component. Others are fine.
(Ed - I didn't mention the ocx did I. It's a Socket/X from Mabry - no reason to beleive there's a problem with the control.)
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