I think the main problem is that I'm running remotely at the client site. I remote into a Citrix box which has MS Access on it and then from there remote into another box which has the VFP 9 IDE.

I'm trying to connect to a proprietary accounting package called Timberline which uses Pervasive SQL. I extract a connection string from MS Access - which will achieve a successfull connection - and then copy/paste into a new Fox Connection and it asks for a data source. When running MS Access the proper DSNs are displayed (specific to Timberline P/SQL) but they don't show as selectable on the Fox-box, mainly, I think, because they're not resident on the box.

I'm really not sure why I would need DSN files, maybe because the database is proprietary. I think all I have to do is copy them over so they reside locally on both boxes, but I wasn't sure.

Thanks for your feedback,

Irv.

>There're diffeent type of DSNs and only one of them ic an actual file.
>

User DSN - avalable to the user that create dit only. Not a file - stored in the registry
>

System DSN - avalable to all users on the PC. Not a file - stored in the registry
>

FIle DSN - it's a file.
>
>Why dom't you use DBC connection with a connection string? It wouldn't require any externalfiles/configurations.
>
>
>>
>>I have a question on the use of ODBC connections between Fox and MS Access via a remote View. When a DSN file is needed for an ODBC connection, must it be on the local C:-drive? The reason I ask is I remote into a Citrix server which has a needed DSN file but then remote over to another server which has the Fox IDE. When I'm on the Fox machine I get an error trying to connect via ODBC in a remote view.
>>
>>I suspect it's because the needed DSN file is no longer 'local' (on my current C-drive). Can I just copy this file over to another c-drive? Any particular place? Also, does it need to be set up or registered in any way?
>>
>>Thanks,