In that sometimes it works for me and sometimes it doesn't.

Grouch # 1. Why doesn't 10/0 generate an error?? I want to see divide by 0 errors, especially when I shouldn't get 0's. Instead I get ******. Eh???

There have been a number of occasions where my error handler, which is very simple, hasn't fired when it should, but I've been unable to track an example down...until now. If I try and put a number (or a date) into a list box row i.e myListBox.List(row,col) = NumberVariable, I get an error (Incorrect data type), but my error handler doesn't fire. Worse, I now have to Ctrl-Alt-Del out of the app to get out of a series of these errors.

Grouch # 2. Why can't I put a number or date into a list box cell without having to convert it? I now have a situation where I have strict typing where I don't want it (list/combo boxes....although it's not difficult to get around) and no typing when I want it (making sure dates are dates and not strings...it's an VFP/ADO/Oracle thing).

That feels better...Can someone please tell me why my error handler doesn't fire and let me know if there any more situations where this occurs. Even better, a solution would be nice (though I'm not holding my breath on this one).

Oh yes, the reason why I don't have the benefit of the debug facilities is that some bright spark made the #INCLUDE a compile directive and not an environment directive...thus forcing me to test using EXE's. I now have the arduous task of converting my constants into object properties and using a VCX instead so I can get my debug facility back...Oh joy..more testing!!!

This shouldn't happen on a friday!!

Thanks in advance.

Pablo