|
-
November 3rd, 1998, 10:58 AM
#1
COM object blows stack in VB application
hi,
i have a VC5.0 COM object (that uses DAO) that is used within a VB4.0 application. i get the dreded "run-time error '28' out of stack space" when my application is parsing a large database using DAO.
basic COM object function:
the COM object reads in text files, parses them and creates/opens/updates the DB appropriately. everything works fine till my input files get large (works when they are ~300Kb, blows when >325Kb, this is approximately 5000 DAO records).
i think this puts a burden on the JET engine.
few questions:
- seems the stack size of my component runs on the VB stack, can i increase the
size of the VB stack? (changing my components stack size doesn't seem to make a difference)
- i ran the VB app (w/my control) through BoundsChecker and it reported "minor" leaks, and most of them were in DAO. is there anything i can do to make DAO conserve more memory? or to have DAO free up its memory (yes, i'm closing/flushing the recordSets/tables when i am done with them)
- do my record size exceed the limits of JET/DAO? anyone know how to find the limits?
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules
|
Click Here to Expand Forum to Full Width
|