>>>>I'm having a problem with my app tossing an error saying a view definition has been changed. Thing is if I run the exact .exe with the exact same .dbc on another machine it works just fine. I'm thinking that the machine that's giving me the error might have the wrong VFP runtimes on it??? Is there a way I can tell which runtimes to use by looking at the compiled .exe? Or am I even looking at the right possibility of this problem?
>>>>
>>>>Thanks!
>>>
>>>Are you using any transformation of the data which may be settings dependable or non fixed length? Say, do you use ctod function in the view or alltrim or anything of this sort?
>>
>>well...not really - this is what the remote view looks like:
>>
>>SELECT Hcfadtl.HCD_PKEY, Hcfadtl.MBIL_DOCNO, Hcfadtl.CPT, Hcfadtl.UNITS,;
>> Hcfadtl.CPT_MOD, Hcfadtl.HCD_NSDATA, Hcfadtl.FROM_DATE, Hcfadtl.TO_DATE,;
>> Hcfadtl.POS, Hcfadtl.BILLED, Hcfadtl.CONTRACTED, Hcfadtl.TPL_AMT,;
>> Hcfadtl.PT_SHARE, Hcfadtl.WRITEOFF, 0 AS linenum, Hcfadtl.CPT_MOD,;
>> Hcfadtl.POS, '1500' AS extension_1;
>> FROM ;
>> KPOPS.HCFADTL Hcfadtl;
>> WHERE Hcfadtl.MBIL_DOCNO = ( ?lnmbil_DocNo )
>>
>>
>>...as you can see it's a very simple view.
>
>Right. Did you try to drop it, compile database, re-create again?


I copied a .DBC that I know is working. I think I may of stumbled onto something though - the machines that are working are using the Microsoft ODBC driver for Oracle - the machine that is NOT working is using the Oracle ODBC driver - not the one provided by microsoft - going to play around and see if I can get the Micro$oft one working on that machine - heck maybe that's the issue...geeeeze.