Nope, but another option would be to open and close the tables as part of the get data process.

>Hi,
>
>I have a small application (that works as an add-on to a large application). The small application does the following: every 1 to 5 minutes (depending on user preference) the app (which is just one form) connects to the data and checks if some new orders were created (by another web-based application). Currently this small app has BIZ object (based on Cursor Adapter class) that does all data access and updates. The problem is that when the large app needs to do any maintenance this small app is "in the way" because it has the data tables opened. That is, when the BIZ object is created in the INIT of the form it opens some tables. I am thinking about changing design and instead of creating BIZ object in the INIT method, create it on every access to the database. Therefore, if I change the program this way, the BIZ object will be created (and then destroyed) every 1 to 5 minutes. Anybody see a problem with this approach? TIA.