Hi Walter,

>Can you explain why you cannot use dbfs and DBCs?

My client said they don't want new FoxPro development in their shop, period.

A good one, heh? So I'm trying to sell them "SQL Server applications", that's meant by a SQL Server database and a FoxPro front end. Hope it sticks, because think their main reason are the DBFs (they don't say much about, just that they don't want... perhaps they're not aware of the fantastic publicity around VFP).

>I use a connection string (SQLSTRINGCONNECT())...

One more question: I use SQLconnect(), and never figured out what is the (difference) advantage of using SQLstringconnect(). Also, I did some experimenting with "dsnless" connections and didn't figured out the advantages. As you can see I'm a rookie in the backend field.

I really would like to jump over the "deployment issues" my client is *also* imposing to client/server (they want, from now on, just web based apps) apps. One of their arguments is having to configure datasources in each user's PCs. If SQLstringconnect() or dsnless connections could overcome that issue, it would be one less.

Regards,

Fernando

>Hi Fernando,
>
>Can you explain why you cannot use dbfs and DBCs?
>
>What I usually do is to create a project with a DBC contaning remote views and dbfs with meta data and INCLUDE that into the executable. So the end product is only the executable, you don't have to deliver DBCs and DBFS, but in fact you are using them since they are IN the executable.
>
>I use remote views for data entry forms, and mainly SPT for queries and populating drow down combos. RVs have the advantage they can automatically change datetimes into date. With SPT you'll have to jump through some hoops to solve that problem. I use a connection string (SQLSTRINGCONNECT()) stored encrypted in a SQLconnect.TXT file in order to connect to the database. In VFP8 and later you can open a view with the connection handle retrieved from SQLSTRINGCONNECT().
>
>HTH,
>
>Walter,