: We have an ACCESS 2.0 query-only appl. ACCESS talks to oracle v7 via ODBC.
: Response times are ok. But after - say - 20 queries ACCESS starts to eat
: memory, the system starts swapping until it hangs.
: I ran the appl under Windows NT, too, where i could see that memory is
: consumed till a system warning msg appears (insufficient virtual storage).
: Could it be that ODBC allocates some memory for each query and forgets to
: free it up?
Yes it does. Actually Windows does this too, in the MDI based applications
every time a MDI child is closed, some memory is not freed. So even without
ODBC you will face such a problem with Access as Access is a MDI.
Recently I ran in to some files on CompuServe with the name memfix.* or
something like that, that should replace some of the memory management
done by windows. Didn't try it yet.
For ODBC, my company has reported this problem to MacroSof, but no action
has been taken on that by MacroSof. So when you are not planning to support
several server platforms in the near future (couple of year), I would
recommend switching from ODBC to a database vendor supplied dblib like thing
to replace ODBC with native support of transfering the SQL and results
between the server and the Acces client.