I'm not sure if this question belongs here or in reports...
I'm running Acc 2003.
I've built a query which uses a function to translate/populate a field within the results. I then built a report based on the query. The function is not used anywhere else in the application.
When I run the report from the design window, the design window goes away, then the query executes and the report gets generated in a preview window. When I revert to design mode the preview window gets replaced with the design window as expected; however, my hard drive spins up, and a process steals cycles from my use, making changes I want to make in the design window slow down. I have discovered that this process is the query running again -- I hit Ctrl-Break and the code interrupts in the module housing the function the query uses; also, if the code window also happens to be open in the background, one can see the window flicker as the process is entered and exited.
Any ideas on why the entry into design mode would cause the query to fire up? If this is an "event" as Access knows it, I hope to put some code there that will stop it from happening.
Thanks in advance.
I'm running Acc 2003.
I've built a query which uses a function to translate/populate a field within the results. I then built a report based on the query. The function is not used anywhere else in the application.
When I run the report from the design window, the design window goes away, then the query executes and the report gets generated in a preview window. When I revert to design mode the preview window gets replaced with the design window as expected; however, my hard drive spins up, and a process steals cycles from my use, making changes I want to make in the design window slow down. I have discovered that this process is the query running again -- I hit Ctrl-Break and the code interrupts in the module housing the function the query uses; also, if the code window also happens to be open in the background, one can see the window flicker as the process is entered and exited.
Any ideas on why the entry into design mode would cause the query to fire up? If this is an "event" as Access knows it, I hope to put some code there that will stop it from happening.
Thanks in advance.
