>Hi Rolf,
>
>>At the beginning the result is ok and looks e.g like this:
>>C:\PATH\CLSLIB1.VCX ALIAS CLSLIB1, C:\PATH\CLSLIB2 ALIAS CLSLIB2, C:\PATH\CLSLIB3 ALIAS CLSLIB3...
>>After some time the result changes like this:
>>C:\PATH\CLSLIB1.VCX ALIAS GODATA_345280178 , C:\PATH\CLSLIB2 ALIAS TABNAME , C:\PATH\CLSLIB3 ALIAS FIELDNAME...
>>or
>>C:\PATH\CLSLIB1.VCX ALIAS , C:\PATH\CLSLIB2 ALIAS , C:\PATH\CLSLIB3 ALIAS ...
>
>Before you get dive headfirst into debugging this issue, you should try to run your program with vfp9,
>as some existing problems with alias names were fixed in either vfp8 or vfp9 (they were definately still in vfp7),
>something I discussed with Aleksey T. from the vfp team back then here on UT.
>
>Seems to be a different bug, but still porting to the last version might make biz sense for such issues
>[debuging in this area can will suck up time if a sporadic factor is involved and
>even otherwise you have to research/read much that will turn out to be not related to the particular issue ;-) ]
>
>There ***are*** still some ways to corrupt vfp9 memory - Calvin has some hints and code in his blog,
>you might adapt it to your program. I have run into similar problems in the last 20 months and
>was able to find/fix some causes using adaptions of Calvin's code and some Systernal tools.
>
>regards
>
>thomas

Hi thomas,

thanks very much for reply. I already tryed the same program with vfp9 and there was no such problem. But unfortunately at the moment we can't replace the runtime at our 1200 customers with circa 25 workstations per customer, so i have to find a usable workaround for this problem.

regards

rolf