Hi, As far as I know, .NET garbage collector does not collect the garbage (in your case factory object) when it is set to nothing, it works unpredictably. So your connection might not get closed if you don't force the garbage collector to do its work using one of the following after setting it nothing:
.Call System.GC.Collect() .Call System.Runtime.InteropServices.Marshall.ReleaseComObject() Hope this helps, Teoman "viktor zaletelj" <[EMAIL PROTECTED]> wrote in message news:[EMAIL PROTECTED] > Peter! > > thanks for the idea, where to track the problem down.... > > i have found the reason for this:: The program opens the CacheObject.Factory > object (new Cache Process), and didn't succeed to close it every time. So > the numeber of processess increases through client requests, until reaching > the unresponsible state of CacheORDBMS. > > I have checked also my ODBC connections. ... but they work fine - after > closing, the particular process goes down. --> Reason for error: After to > many opened processes (by Factory objects), the ODBC request fails. So i > suspect, that ther should be something wrong with the ODBC connection - but > i was wrong! > > Reconfiguration and instant check about Factory object give me good results! > > Thanks a lot again! > viktor > > > "Peter Cooper" <[EMAIL PROTECTED]> wrote in message > news:[EMAIL PROTECTED] > > Viktor > > > > Suspect that you are opening lots of ODBC connections rather than open > > one and re-use it > > > > The sort of calculations that happen are > > a) upto 12 connections form the same IP take 1 license slot > > b) the 13th takes 13 license slots > > c) every further one from the same IP adds 1 to the license count > > > > so if you have a 20 user license then this is when it bombs > > > > Have a look at $System,License.Help() - there are calls here that will > > track this down > > > > Peter > > > > On Sun, 11 Jul 2004 23:44:55 +0200, "viktor" > > <[EMAIL PROTECTED]> wrote: > > > > >Hi! > > > > > >i'm working with the CACHE through the MS .NET framework. > > > > > >Through development phase, everything works fine, but now(testing) i > > >encountered problems with simple ODBC request: > > > > > >SELECT * FROM Splosno.Oseba WHERE ORDER BY Splosno.Oseba.id desc > > > > > >It works fine until i the 20th request, when i got a message: > > > > > >ERROR [S1000] [Cach� ODBC][State : S1000][Native Code 98] > > >[C:\WINDOWS\Microsoft.NET\Framework\v1.1.4322\aspnet_wp.exe] UNKNOWN MSG > > >ERROR [01000] [Microsoft][ODBC Driver Manager] The driver doesn't support > > >the version of ODBC behavior that the application requested (see > > >SQLSetEnvAttr). > > > > > >From this moment, my application can not connect the ORDMBS any more. > > >I noticed ODBC errors note in Cache Control Panel :: > > >coloumn(SQLCode)=<-98>:<Licence violation>, coloumn(Cache Error) = > Nothing > > > > > >The connection was established through the ODBC. I have tried also with > the > > >ResultSet object, ... and the same happens, insted of error ::: Factory > can > > >not be connected to DB. > > > > > >Any idea? .... is there any limit in free version in described sense? > > > > > >Thanks for help > > >viktor > > > > > > >
