X
XIntel1955
To whom it may concern: 1/29/07
Here are the 2 questions I have pertaining to the Access anomalies that I’m
currently seeing.
1. Why does my MS Access application appear to freeze sometimes?
Algorithm:
•The program processes data from DAO 3.6 RecordSets and then outputs the
contents of a temporary table to the HardDrive as a MS Excel CSV file via the
“TransferText†function.
•The program will process and output anywhere between 1 and 6000 CSV files.
*During the processing of the files, I have a pop-up form displaying which
ticket is currently being processed (textbox) and the overall status of the
application (ActiveX – Microsoft ProgressBar Control 6.0)
•At the start of the application, all begins normally.
•The CPU execution graph is at 95% - 100%.
•Then, “sometimesâ€, the application will place a MS Access icon down on the
main task bar (next to the START button) which indicates to me the task was
minimized when in fact all the application’s forms are still being displayed.
•Then all subsequent screen updates stop thus leaving the User with the
impression that the application has froze; HOWEVER, only the screen updates
have stopped. The file creations and output to the HardDrive continues until
completion of the User selected range.
2.Why does my MS Access application executable grow in size after execution,
and how do I stop this from occurring?
Algorithm:
•Same MS Access application from the previous question executes. Whether the
program terminates normally or enters the perceived “frozen†state, the
application MDB file grows in size.
•The temporary data tables created by queries and processed using DAO 3.6
methods, are deleted upon program termination via DoCmd.DeleteObject
TableName.
•I have visually verified that the temporary tables are gone and the
permanent tables have not been altered.
•What is being added to the application’s executable file and what impact
does it have to normal operation over time?
Specs: OS – XP sp 2.0 Home Edition v 2002
Processor Scheduling – Programs over BackgroundServices have Thread
priority (which may be the answer to my first problem)
Memory – 1 Gbyte
MS Office: XP Version 2002
Access References:
-Visual Basic for Applications
-Microsoft Access 10.0 Object Library
-OLE Automation
-Microsoft ActiveX Data Objects 2.1 Library
-Microsoft DAO 3.6 Object Library
Here are the 2 questions I have pertaining to the Access anomalies that I’m
currently seeing.
1. Why does my MS Access application appear to freeze sometimes?
Algorithm:
•The program processes data from DAO 3.6 RecordSets and then outputs the
contents of a temporary table to the HardDrive as a MS Excel CSV file via the
“TransferText†function.
•The program will process and output anywhere between 1 and 6000 CSV files.
*During the processing of the files, I have a pop-up form displaying which
ticket is currently being processed (textbox) and the overall status of the
application (ActiveX – Microsoft ProgressBar Control 6.0)
•At the start of the application, all begins normally.
•The CPU execution graph is at 95% - 100%.
•Then, “sometimesâ€, the application will place a MS Access icon down on the
main task bar (next to the START button) which indicates to me the task was
minimized when in fact all the application’s forms are still being displayed.
•Then all subsequent screen updates stop thus leaving the User with the
impression that the application has froze; HOWEVER, only the screen updates
have stopped. The file creations and output to the HardDrive continues until
completion of the User selected range.
2.Why does my MS Access application executable grow in size after execution,
and how do I stop this from occurring?
Algorithm:
•Same MS Access application from the previous question executes. Whether the
program terminates normally or enters the perceived “frozen†state, the
application MDB file grows in size.
•The temporary data tables created by queries and processed using DAO 3.6
methods, are deleted upon program termination via DoCmd.DeleteObject
TableName.
•I have visually verified that the temporary tables are gone and the
permanent tables have not been altered.
•What is being added to the application’s executable file and what impact
does it have to normal operation over time?
Specs: OS – XP sp 2.0 Home Edition v 2002
Processor Scheduling – Programs over BackgroundServices have Thread
priority (which may be the answer to my first problem)
Memory – 1 Gbyte
MS Office: XP Version 2002
Access References:
-Visual Basic for Applications
-Microsoft Access 10.0 Object Library
-OLE Automation
-Microsoft ActiveX Data Objects 2.1 Library
-Microsoft DAO 3.6 Object Library