Hello. I run several queries daily to help my users identify cases from our hospital database. I have a view of the Oracle db in Access that allows me to do this. It is a highly normalized design with tons of tables required to make a nice report. Periodically, these tables are updated in production, or new ones are added, after which I need to update the views I have by using linked table manager. As you know, Access decides what to call the primary key and this is often wrong.
Since the last two times this occurred, my technique of running a macro to output a report via email is running ridiculously slow. I have had our Oracle/Access person over to help me, and he used VBA to delete the extraneous indexes, and in some cases all of them. The problem persists. I have tried running the steps manually, and exporting a report to any type of file runs too slowly. The only thing that works is to export a query to Excel. This is obviously not as nice for my users.
I'm not sure how much more detail to provide. It's a little frustrating because the IT person I need for help doesn't have time to resolve this issue for me and I'm not sure I can be clear enough.
I am using queries and reports that have always worked quickly in the past. I am an old DB-2 programmer so I understand SQL, but not Visual Basic. This is a sideline on my job today.
I was on Access 2003, upgraded to 2007 recently.
Thank you, Kathy
Since the last two times this occurred, my technique of running a macro to output a report via email is running ridiculously slow. I have had our Oracle/Access person over to help me, and he used VBA to delete the extraneous indexes, and in some cases all of them. The problem persists. I have tried running the steps manually, and exporting a report to any type of file runs too slowly. The only thing that works is to export a query to Excel. This is obviously not as nice for my users.
I'm not sure how much more detail to provide. It's a little frustrating because the IT person I need for help doesn't have time to resolve this issue for me and I'm not sure I can be clear enough.
I am using queries and reports that have always worked quickly in the past. I am an old DB-2 programmer so I understand SQL, but not Visual Basic. This is a sideline on my job today.
I was on Access 2003, upgraded to 2007 recently.
Thank you, Kathy