Performance problem with DAO-application under W2K
Winfried Kaiser, Fortune Systems GmbH & Co.
as compared to the very same application on WIN98, we have investigated
deeper and found a very strange behaviour:
DB access from our VB/DAO program apparently uses an automation interface to
MSACCESS!
In the W2K process-list "MSACCESS" is active, utilizing a considerable
amount of CPU-time. (We did not activate MSACCESS!)
If we cancel the MSACCESS process, our program can no longer access the
Database and receives automation errors!
Why, for god's sake, our software uses MSACCESS automation to access the
Database??? And, more important, how can we prevent it from doing so??
Under WIN98 this does not happen at all!
I am pretty sure to have seen an information in the MSKB on that topic (not
realizing it's relevance then), but, try as i may, I just can't find it
anymore.
Anybody has any solution on that problem????
--
Winfried Kaiser, Fortune Systems GmbH & Co.
Germany
eMail: lo...@fortune.de
Web: http://www.fortune.de
JohnFol
get automation errors. Both Access and VB use JET to access data, it's just
that people refere to it as an Access database and not Jet database.
In your references you need DAO (whatever version). In your code where you
have used the Access automation object you will need to re-write things to
use the DAO reference. If you have an example of your code where you
automate Access, please post it and I'll try and give you a DAO equivalent.
Regards
Winfried Kaiser, Fortune Systems GmbH & Co. wrote in message ...
Winfried Kaiser, Fortune Systems GmbH & Co.
Henry Habermacher
kannst du bitte das crossposting beenden?
danke
--
Henry
ProSoft, Phuket, Thailand
I don't reply to postings in newsgroups. don't even try.
faq: http://www.donkarl.com
app: http://www.accessprofipool.com
Winfried Kaiser, Fortune Systems GmbH & Co. schrieb in Nachricht ...