By |
Testing All UDMs |
mikejlb 10/19/2009 1:56:42 PM | After finding many questionable UDMs running Test All UDMs, I used the profile table to edit the active status in my UDMs. I had hopes of saving time. I created 3 new sub folders in c:2004 and copied mdb files into the 3 folders. One folder to store testing UDM, one folder to store working UDM for daily reports, and one for the origional.
Last night I copied the test udm to the 2004 folder and this copy has all 2009 positive roi turned off. I found this morning that the last UDM took 6 hours to complete. This is a simple UDM that should take 30 minutes maybe doing 2008.
I think there's a flaw in this plan but I'm not sure if I should abandon the idea?
|
jeff 10/19/2009 2:45:33 PM | Mike,
Without seeing the UDMs in your c:\2004\JCapper.mdb file it's impossible to say with 100% certainty...
But my first best guess would be that one or even several UDMs in the file has a UDm Definition that makes it behave exactly the same as if you were running an ALL button query.
If you need help with it shoot me a copy of the .mdb file and I'll have a look.
-jp
.
|
mikejlb 10/20/2009 4:58:53 AM | I posted a dumb question because I didn't think about what the program was doing. The time indicated between query start and query end is the time it takes to run a query. I was running All UDMs and the query start is when I started. As each udm comes on the screen it shows the time that that particular UDM ended but the total time is represents all the UDMs since the start.
Nothing wrong with the way the total time is handled, I must have been found that problem before my 1st cup of coffee.
|