Access 2003 upgrade - user unable to launch parameter queries, or use Report preview button.
Since upgrading a number of users to Access 2003 (Office 2003 Pro ) on new Dell GX-520s with identical images, one user only is unable to use parameter queries or the report preview button, which then prompts her for a number of parameters.
When I log on remotely to the PC as myself (admin) or as the user, the DB works properly. When she accesses it locally, she experiences the problems. All other users on identical new equipment can access and use the db correctly.
I've set Macro Security to low, turned off DEP for the app, checked for missing references, but I still cannot resolve this.
Thank you,
EBM
When I log on remotely to the PC as myself (admin) or as the user, the DB works properly. When she accesses it locally, she experiences the problems. All other users on identical new equipment can access and use the db correctly.
I've set Macro Security to low, turned off DEP for the app, checked for missing references, but I still cannot resolve this.
Thank you,
EBM
does the app work correctly for her on a different PC?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
The app works correctly for other users on other pcs. I do not think that the user experiencing the issues has logged in to our network on another pc as herself to test the app....
Just an long shot, but do a Compact & Repair of that MDB ... from the machine in question. Believe it or not, I just had a very similar issue ... and that solved the problem. That's the good news. The bad news: No Clue Why!!!
mx
mx
Also ... might as well throw in a Decompile. Note: of course all users need to be out of the mdb during the C&R and/or Decompile. Again ... another long shot!
Follow this procedure:
1) Compact and Repair
2) Execute the Decompile >> you database will reopen
3) Close the mdb
4) Open the mdb ... and then do a Compile.
5) Close
6) Compact and Repair one more time
Try this and see what happens
Here are sample 'links'. Adjust your paths and file names accordingly:
Run this from Start>>Run.
"C:\Program Files\Microsoft Office\Office\Msaccess.exe
"C:\Program Files\Microsoft Office\Office\Msaccess.exe
"C:\Program Files\Microsoft Office\Office\Msaccess.exe
"C:\Program Files\Microsoft Office\Office\Msaccess.exe
"C:\Program Files\Microsoft Office\Office\Msaccess.exe
mx
Follow this procedure:
1) Compact and Repair
2) Execute the Decompile >> you database will reopen
3) Close the mdb
4) Open the mdb ... and then do a Compile.
5) Close
6) Compact and Repair one more time
Try this and see what happens
Here are sample 'links'. Adjust your paths and file names accordingly:
Run this from Start>>Run.
"C:\Program Files\Microsoft Office\Office\Msaccess.exe
"C:\Program Files\Microsoft Office\Office\Msaccess.exe
"C:\Program Files\Microsoft Office\Office\Msaccess.exe
"C:\Program Files\Microsoft Office\Office\Msaccess.exe
"C:\Program Files\Microsoft Office\Office\Msaccess.exe
mx
DatabaseMX:,
I have also had cases of "Queries gone Wild".
Where after you save and close a query, the run it again, it may ask for a "Query1" parameter.
If I copy the query and run the copy, it runs fine!
:O
I have heard that if you save the query in design view, you force it to Re-index, re-build, or recompile
Do you have any insites on this?
Jeff Coachman
I have also had cases of "Queries gone Wild".
Where after you save and close a query, the run it again, it may ask for a "Query1" parameter.
If I copy the query and run the copy, it runs fine!
:O
I have heard that if you save the query in design view, you force it to Re-index, re-build, or recompile
Do you have any insites on this?
Jeff Coachman
""Queries gone Wild". ... LOL .... how true, how true!!!
"I have heard that if you save the query in design view, you force it to Re-index, re-build, or recompile "
That is the theory. Save in design view. Jet optimizes the query at that time ... per existing (quantity of) data at the time in the tables concerned. But, supposedly ... if you then run the qry ... and *then* Save, you undo that optimization.
Also, Compact & Repair is *supposed* to re-optimize queries, along with other chores like house cleaning, index verification, etc. But honestly (of course), I have seen some conflicting info on the subject (duh).
One reason I **rarely** use SQL ('queries') in VBA code is that they cannot be optimized per se by Jet ... not to mention the fact that they are just plain messy to deal with in every respect. 'Saved' queries - in the database container - are 'cheap' so to speak ... and I have done some flat ass amazing things with queries ... which makes me reeeeeally appreciate what Jet can do!!! .... And that some VERY smart folks created Jet.
mx
"I have heard that if you save the query in design view, you force it to Re-index, re-build, or recompile "
That is the theory. Save in design view. Jet optimizes the query at that time ... per existing (quantity of) data at the time in the tables concerned. But, supposedly ... if you then run the qry ... and *then* Save, you undo that optimization.
Also, Compact & Repair is *supposed* to re-optimize queries, along with other chores like house cleaning, index verification, etc. But honestly (of course), I have seen some conflicting info on the subject (duh).
One reason I **rarely** use SQL ('queries') in VBA code is that they cannot be optimized per se by Jet ... not to mention the fact that they are just plain messy to deal with in every respect. 'Saved' queries - in the database container - are 'cheap' so to speak ... and I have done some flat ass amazing things with queries ... which makes me reeeeeally appreciate what Jet can do!!! .... And that some VERY smart folks created Jet.
mx
Thanks for the info!
:)
:)
Jeff ... see the other Q we are working on "Ctrl space complete word sh..."
I just added more to that ...
mx
I just added more to that ...
mx
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
<I have heard that if you save the query in design view>
My understanding was slightly different, that the query only gets optimized the first time it is actually executed. Like DMX posted, you save the query after you make changes but before you run it. With my poor SQL skills I typically run it, change it, run it, change it etc. When I finally get the results I am looking for I use a trick I read in ADH which is to simply add a space and then remove it from the actual SQL, then I do a final save and then run.
My understanding was slightly different, that the query only gets optimized the first time it is actually executed. Like DMX posted, you save the query after you make changes but before you run it. With my poor SQL skills I typically run it, change it, run it, change it etc. When I finally get the results I am looking for I use a trick I read in ADH which is to simply add a space and then remove it from the actual SQL, then I do a final save and then run.
stevbe:,
Thanks to you as well!
:)
Jeff coachman
Thanks to you as well!
:)
Jeff coachman
ASKER
I will not have access to this file on the PC experiencing the problems until my agency reopens on April 11th.
I will update this question at that time.
EBM
I will update this question at that time.
EBM
ASKER
I had the opportunity to work with the problematic Pc/DB today, and here's what is now evident;
Any DB run on this new PC (Win XP SP2) in Access 2003 launches, but Reports can not be created, run, or previewed - they simply do not appear to launch, UNLESS the user logged in has local
No other functionallity appears to be effected, only Reports.
Administrative rights. I've deployed 60 of these identiclaly imaged machines over th elast 40 days, and this is the only one I''ve see nthis behhavior on... Help!!!!!
EBM
Any DB run on this new PC (Win XP SP2) in Access 2003 launches, but Reports can not be created, run, or previewed - they simply do not appear to launch, UNLESS the user logged in has local
No other functionallity appears to be effected, only Reports.
Administrative rights. I've deployed 60 of these identiclaly imaged machines over th elast 40 days, and this is the only one I''ve see nthis behhavior on... Help!!!!!
EBM
is it a case of the local user (non-admin) does not have rights to install the printer driver from the network ... any report previewing in Access requires the OS has a default printer properly installed.
As per my original post, symptoms point to a corrupted or outdated printer driver on that PC.
ASKER
All users have the rights to add a printers on their PCs. They do so by finding them in the directory, then adding the printer. The appropriate drivers are ,a of course, installed without issue by default...
EBM
EBM
How do know the installed driver has not been corrupted? Try downloading and installing the latest printer driver for the problem pc even if it is the one you already have.
ASKER
Reinstalling the current printer driver has had no effect on this issue, which I now see on 2 different PCs in the same domain.
I've removed the server-based printer object completely, reinstalled it on our server, and reinstalled it on the two affected PCs. The problems remain.
I can workaround this issue by setting the default printer on the PCs to one of our networked copiers, or to the MS Document Imaging driver, but my users have to choose their printer from the file menu...
Any additional suggestions ?????
EBM
I've removed the server-based printer object completely, reinstalled it on our server, and reinstalled it on the two affected PCs. The problems remain.
I can workaround this issue by setting the default printer on the PCs to one of our networked copiers, or to the MS Document Imaging driver, but my users have to choose their printer from the file menu...
Any additional suggestions ?????
EBM
<Access requires the OS has a default printer properly installed.>
<setting the default printer on the PCs to one of our networked copiers,>
so their is already a default printer set up correctly on the PC before they try to open a report? I think this also needs to happen before they open your app at all. Access absolutely requires a printer in order to preview, much less print a report.
Steve
<setting the default printer on the PCs to one of our networked copiers,>
so their is already a default printer set up correctly on the PC before they try to open a report? I think this also needs to happen before they open your app at all. Access absolutely requires a printer in order to preview, much less print a report.
Steve
"Access absolutely requires a printer in order to preview, much less print a report."
In fact, you cannot even design a report w/o a default printer set. However, 'any' default printer will do (for getting started in report design) ... even the Windows fax printer, etc.
mx
In fact, you cannot even design a report w/o a default printer set. However, 'any' default printer will do (for getting started in report design) ... even the Windows fax printer, etc.
mx