I have tried several designs to handle the data connection object for our Web application. I haven't been able to figure out one that would be perfect. I would be interested to hear about how you all do it in your Web applications. As for me, I have tried the route of using one global connection object but that fails sometimes when two simultaneous hits are hitting the server. Basically, the second hit would collapse on the other one, as far as the connection object goes. So, this would create an object reference not found on the second hit. Then, I tried the route of having the connection object to be created at every hit. The problem with that is the VFPOleDb data provider is failing sometimes when being used on a high frequency. That, I wouldn't have a problem with SQL Server. However, I need to support VFP for a while. So, how are you using it? Has anyone found a way to only create the connection object at once and be able to use it all the time without any problem when two simultaneous hits are hitting the server? Because, creating it at every hit takes about .03 second more. And, this still doesn't resolve my problem under VFP.