I named the DSN file exactly the same in the client's computer, and still, i had some problems. I noticed that the ODBC DSN files were saved in different folders in the dev. computer ( Win2k machine ) and the clients computer ( Win98 ), so maybe there is the problem.
OTOH, i'll probably use InstallShield, since i guess i'll run again into this problem, and i have to distribute a big app soon in a very large Wan.

Thanks a lot for your help!
Jaime

>I remember your earlier post about getting the RDC to work - glad to see that you got that going. :)
>
>In general, Crystal likes to use the exact DSN name that was used to create the report. That means if, for example, you created the report to use a free-table VFP ODBC DSN named "Report Source", you cannot expect the report to work on another machine with a DSN named "ReportSource".
>
>It is possible at runtime to change the DSN associated with each table on the report by making use of the SetLogonInfo method of each table object, passing it the name of the DSN to use.
>
>From a distribution standpoint, I use InstallShield to install our application at our client site. Through IS, I'm installing the core ODBC components and also instructing it as to which DSN's to create at installation time.
>
>Hope this is helpful.
>
>Laterness,
>Jon