Hi,

>>Can you clarify what you mean here. It sounds as if you expect to place a copy of a SQL database on the customers machine and access it via the VFP OLEDB drivers without an installed instance of SQLServer. You can't do that.
>
>No, the accountant would have sql databases (accessed as a service) whilst the customer would have one or more sql databases with native/odbc access (sql - not VFP this is)
>I'm planning to convert the foxpro databases

Sorry, but I'm still not clear on what you are proposing. It still sounds as if you intend for customers to have their own copy of the data on their machine. If so, regardless of whether you are accessing it from VFP or .NET, they will need an instance of SQL server installed. The only alternative (AFAIK) would be to use the CE standalone database (SDF) files. In that case there are a small set of .NET DLLs that can be embedded in your application so that no SQL installation is required. That may or may not be a viable option - this information might help: http://download.microsoft.com/download/A/4/7/A47B7B0E-976D-4F49-B15D-F02ADE638EBE/Compact_Express_Comparison.doc

HTH,
Viv

>
>The folder structure would look like
>
>

>root
>    - cust_1
>        - 2004
>             2004.mdf
>        - 2005
>            2005.mdf
>       ...
>
>    - cust 2
>       - 2006
>            2006.mdf
>       - 2007
>            2007.mdf
>       ....
>
>    - ...
>
>

>Does this make more sense ?
>
>[ I have also thought about sql compact for the customers, but then I would need to maintain 2 database structures and pull data from one into the other]
>
>____________
>>Hi,
>>Snips:
>>The accountant would have an sql server whilst the customers would access the database with the native drivers.
>>There are many customers - installing/maintaining an sqlserver service is not feasible in terms of work/problems
>>
>>Can you clarify what you mean here. It sounds as if you expect to place a copy of a SQL database on the customers machine and access it via the VFP OLEDB drivers without an installed instance of SQLServer. You can't do that.
>>Regards,
>>Viv