|
|
Database connections
Posted: 09 Sep 09 10:28 PM
|
I have a question related to database connections the Omni Server opens during such function calls as CreateValidationRemote(), etc, and when the .ITC file is transmitted and processed.
Does the code written by the ITScriptNet developers close each database connection upon successful function execution?
In any of the code I have written, I use the Close command and subsequently set the connection object to Nothing (e.g. adoConn.Close followed by Set adoConn = Nothing). I also use the same method in the After Processing script when I have completed all processing (using a single connection passed between scripts via ObjList().
I am attempting to answer a question definitively that there would not be an ever increasing number of concurrent connections from the Omni Server to the database. The exception being if some untrappable error prevented code execution from reaching the close connection commands, but that should be rare enough.
Mark Robinson |
|
|
John Lathem
Posts: 76
|
 |
|
Re: Database connections
Posted: 10 Sep 09 8:35 AM
|
Yes, the OMNI Server opens and closes the database connection on each call to CreateValidationRemote, or when generating validation files for upload. When the ITC file is processed, the connection is opened once at the start of the file, held open while each record is processed, then closed at the end.
Are you seeing a problem with connections being left open, or are you just making sure it won't happen?
Thanks! |
|
|
|
Re: Database connections
Posted: 10 Sep 09 9:09 AM
|
I am just making sure I have a definitive answer available on how all database connections are handled, regardless who wrote the code.
Thank you! |
|
|
|
|