>I have a SQL/VFP design question
>
>I'm now using SQL 7 in my app, instead if VFP tables.
>
>For each user that starts an instance of my application, I was
>thinking of storing the connection handle from the SQLConnect command
>to a property on my App object, and maintaining that connection as
>long as that instance of my application is open.
>
>Any ideas on this?
>
>Thanks

I like the idea but there are some issues to take into account.

Depending on the number of users simultaneously hitting your application, if you don't have the licenses for it, you can't really do this. If you have a limited number of license then you have to establish the connection each time and release it when the task is complete. This has a big impact on performance but it keeps license costs down.

The other thing to worry about is error checking. Establishing a connectino up front means you have to be able to trap if it goes down for some reason. Establishing it each time leaves a slim chance that the connection will be severed in the middle of task. Establishing it once leaves a big open dorr for something to go wrong.

However, if you have the licenses and your error trapping is robust, the performance boost outweighs any other things, IMO.

HTH.