Hi Cetin,

>I think I'm not a newbie to VFP and using VPM for months (w/o my will). If this is the same product from promatrix (VPM6.0b) then there should be something wrong with me. Am I missing something ? You say it "has" error handling. Where ? Only thing I could find is "errors" menu item where you can only check "status" and "memory" at the time error occurred. I couldn't do a real debugging yet. How to do it ? Many times I find myself writing :
>"on shutdown
>quit"
>in command window for I just merely misspelled a table or variable name. Well those are easy to find and fix but there are some that I really want to be able to use "debugger". How could I ?

Personally I don't use the VPM Error handler within the development environment for the same reason's you gave, but in the field, I like it, because it give me valuable information afterwards, because if you ask the user, what was the error-message, it says something like variable thisorthat not found, very helpfull, NOT.
But VPM listes to the developers, because in the next version, VPM Enterprise (now in Beta) global variables are no longer used (oApp, oMessage etc), they are now all properties of _screen (_screen.oApp etc) so when you use the debugger and "FIX" something, all references are still intact.

>I don't want to be antipromoting but I have real doubts. I killed my own persistent relations just for the sake of VPM cannot handle it in one_to_many. If you're developing a simple project then it's OK. Anyone later checking project could resolve relations. What if you have many tables ? You don't have an option to see relations at a glance in DBC.

For that I use xCase, that is a great modeling tool for desinging databases.
Hank Fay (www.prosysplus.com) has created an interface call xCase2VPM (and VPM2xCase) to use them together. It should become an commercial product, sold by ProMatrix, real soon. I have used the beta-version of it, and I can't live without it. I can't imagine desinging a database without xCase.

>Another point is that most of the time object names are hardcoded :( Why should I always have grdChild in pgfChild pages ?

I think you mean grdRelated of pgfRelated, but I know what you mean. But that's with 3rd party frameworks, some things you have to live with. Just like oApp, personaly, I would have prefered oFrank but that's another story <vbg>

>Yes you could go and change source code (really ?) and honestly I did that too. What happens when a new version arrives ? Well I extended 2tier subclasses to 3tier to be able to protect myself from version changes but definitely that doesn't mean I would be free of checking my code changes.

I use 4tier subclasses, but for me the benefits are greater that the opposite.
But I agree, it should be better.

Jack says code is rock solid but I found bug in code in the first day I started to use VPM6.0. There are still bugs in 6.0b. Newsgroup catches some and how many left ?

Of course, it would be best if there were no bugs left in the (software-)world, but I find there are little bugs (left) in VPM.

>Well try only this one :
>
>-create a table with 2-3 fields which all are FK.
>-Set their relations to a lookup table.
>-Create a form and for all fields set lLookupDescription = .t. and set needed properties like cLookUpFKTag etc.
>-Run form. Voila no problem and you can enter records.
>-Now delete all records (no zapping)
>-Try to run form :(

I will try it, but have you posted this problem on the promatrix newsgroup?

>Well only if I could find an answer to "debugging" I could live with it.

You know VPM (the development platform) has admin-tools also, there you can deselect the error handler, and voila, vfp error are back (messages that is <s>)

>Cetin

hth,
Frank Camp
Microsoft MCP (Foxpro)
Visual Promatrix MVP