Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
Trying to know what makes the database non restorable
Message
From
23/03/2017 17:52:01
 
 
To
All
General information
Forum:
ASP.NET
Category:
Databases
Title:
Trying to know what makes the database non restorable
Environment versions
Environment:
VB 9.0
OS:
Windows 8.1
Network:
Windows Server 2012
Database:
Visual FoxPro
Application:
Web
Miscellaneous
Thread ID:
01649277
Message ID:
01649277
Views:
54
I am trying to know what remains tied to the database. I have an application which starts, does some selects, and from a button I need to restore a new copy of the database. That cannot be performed as the procedure confirms the database cannot be used exclusively.

I made a small adjustment to the data model to avoid any process at startup. If this is the case, I can execute the procedure properly.

However, I need to find what causes the data class to have an object linked to the database.

I am using an approach like this for each select:
Using loSQLConnection As New SqlConnection(oApp.aConnection(nConnectionString, 1))
   oCommand.Connection = loSQLConnection
   oDataAdapter.Fill(oDataSet)
End Using
I always assumed the connection was created on demand and close immediately.

Each of the select using that code performs other procedures such as dumping the first record find into a datarow. But, once the datarow is initialized, there shouldn't be any link remaining with the code that was executed in the Using\End Using syntax.

Anyone could have an idea what is the cause there would be an open connectivity to the database?
Michel Fournier
Level Extreme Inc.
Designer, architect, owner of the Level Extreme Platform
Subscribe to the site at https://www.levelextreme.com/Home/DataEntry?Activator=55&NoStore=303
Subscription benefits https://www.levelextreme.com/Home/ViewPage?Activator=7&ID=52
Next
Reply
Map
View

Click here to load this message in the networking platform