J
J French
Can anyone tell me why a Visual Basic 6.0 app running on Windows XP embedded
would give a run time error 5 when calling one of the following functions?
Mid
Left
Trim
InStr
I've been following this thread, and have one more suggestion.
At the top of every Module, Form etc put:
Option Explicit : DefObj A-Z
It is just possible that you have some Deviants (variants) turning up
as a result of (ahem) incomplete declarations, and under certain
circumstances they are confusing things.
Another point, always test with Ctl [F5], in some shops just using
[F5] is a sackable offence.
Also, sometimes VB is not totally honest with its Errors, when it gets
very confused it can also get misleading.