>>Now a new question, has anybody else noticed that the development environment gets really Dr Watson prone when passing around DS ID to manipulate the current DS ever since SP3? I've crashed burned ever time I mess with passing a DS ID ever since SP3, never could put my finger on a specific bug but I've bitched and moaned a whole lot regarding this.
>
>You are probably looking for a different perspective, but I still use the oApp properties to do this. The oApp object was created at launch time in the VFP Default DS. By letting oApp handle the changes or store the DS in a property you want to be/remain current, I do not have such problems during development or run time.

Actually was looking for a different perspective from my own, and you're giving me that just fine =D) My hassles with passing DS id's was between forms that sometimes use the calling form's default data session and sometimes don't. So glad to hear it was probably just me being thick headed (which is what I expect any how) & not a real bug.

>I have a small PRG that I only run at development that sets up my oApp object, etc., to help simulate the run time environment.

< big smirk > Buddy... Pal.... Dear Sweet Mark... Have I mentioned lately how much our friendship means to me? < snickering > Any chance I can peak at that prg?