>>But isn't there a limit on how many connections user license allows? I don't know why and where I got that it is better practice to just open one connection and keep it for the duration of the application. Also, I would be concerned (if connecting on every hit) that it would slow down the application. But thank you for your input; something to consider.
>
>If you take the context of a Web application, you cannot share a connection across hits as this will and can overlap on each other. A connection is created for a fraction of a second, the time to process the hit, and disappear after. So, those are not simultaneous connections, at least not thousands at the same time, which are then 2, 3 or 4 depending on the time of day.
>
>This applies to Web and Web Services.
>
>As far as the Robot application, the desktop type application which answers the Web or any other needs, it loops every minute and will issue a connection for the time (duration) of the loop, which lasts for about 3 to 15 seconds depending on how many processes there has to be done. As far as desktop application with users being the keyboard, I have seen context where they open and close for every SQL Server requests. Some others will keep one for a while and so on. I guess this one requires a more in dept analysis on its setup.

My application is a Desktop type (typical VFP application). But I will - hopefully soon - start converting it to a web-based. So all your input is very useful. Thank you.