Dlookup in function, is there a way around?
Hiya.
First off i'm in access02, I have a big nasty query that pulls data from local tables as well as a remote table elsewhere on the lan. The remote table is in access97 and is generated by our phone system reporting software and can't be modified. When running the report(or query for that matter) with the phone system data included, it can take up to several hours to run depending on the time of the month. If I strip away the phone data, the report/query will run in under a minute. Recently I've had to add vb script to the report that performs dLookups on another table. With that function in place the report will not run, period. I've left it for 36 hours and it will sit idle with the status bar full of little blue dots.
I guess my question is really about optimization and why the insane slowness. I've tested the network and speed shouldn't be an issue there. I can run the reports from a third location, accessing both tables remotely, and find the same results. I limit the recordset in the phone table with a query, prior to the one that feeds the report, but it doesn't alter the horrendous run time. I know this is probably an impossible question to answer, but any help would be greatly appreciated.
Sorry for being so long winded.
-shane.
Hiya.
First off i'm in access02, I have a big nasty query that pulls data from local tables as well as a remote table elsewhere on the lan. The remote table is in access97 and is generated by our phone system reporting software and can't be modified. When running the report(or query for that matter) with the phone system data included, it can take up to several hours to run depending on the time of the month. If I strip away the phone data, the report/query will run in under a minute. Recently I've had to add vb script to the report that performs dLookups on another table. With that function in place the report will not run, period. I've left it for 36 hours and it will sit idle with the status bar full of little blue dots.
I guess my question is really about optimization and why the insane slowness. I've tested the network and speed shouldn't be an issue there. I can run the reports from a third location, accessing both tables remotely, and find the same results. I limit the recordset in the phone table with a query, prior to the one that feeds the report, but it doesn't alter the horrendous run time. I know this is probably an impossible question to answer, but any help would be greatly appreciated.
Sorry for being so long winded.
-shane.
Last edited: