I converted an Access 97 front-end app to Access 2000. This app is full of questions that the user can select to produce needed reports. Problem: When I click on a question button, instead of making a report, the explorer screen pops up and displays the directory! However, if I punch F11, go to the reports directly and click on them, they come up appropriately. I really need the users to be able to just click on a question button rather than get into the tab section of reports. Any ideas? Maybe a glitch in the Forms section? (I'm a novice user yet.)
Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations bkrike on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
Converting 97 Front End to 2000 1
- Thread starter PAWelch
- Start date
-
1
- #2
PAWelch:
I may be the bearer of bad news here, but if there is one thing I've learned the hard way, it's that Microsoft has not made transitions to newer versions of Access very easy. As a matter of fact, I had done the same thing a few years ago, and it turned out MS chose NOT to include a translator for some of the functionality I was using in 97. It required a complete rewrite to make it work in 2000.
I quickly discovered that I was not the only person in my organization that had this problem. There were many irate people here.
But in trying to give you suggestions, you might want to take a look at the references which are loaded with Access 2000 and compare them with the references your 97 version was using. Sometimes that's all you need to do to get things back on track.
Open a copy of the 97 db in Access97. Press Ctrl + g which will take you to the Visual Basic code screen having a lower window titled Immediate. (While you don't need that window, the Crtl + g method is a quick and dirty way of getting the VB code screen.)
On the menu bar select Tools, References. A small window will pop up listing all the references. Make note of all that are checked.
Now open the 2000 copy in A2K, and use the same method to get to the VB code window, and then the references window. First check if any of the references are marked as MISSING. If there are any, it means you need to browse thru your hard drive to try to locate them.
If there are any references from the 97 version that don't appear in the 2000 version, scroll down the references list until you find them and check them off. Hopefully this will correct your problem.
If it doesn't then you need to open in design mode, the forms containing the buttons. Select the button, and from its property sheet find out what its OnClick event code says. You may have to change the coding to point it in the right direction.
There are many threads throughout these forums discussing references. You might want to search them out to learn more about them.
HTH,
Vic
I may be the bearer of bad news here, but if there is one thing I've learned the hard way, it's that Microsoft has not made transitions to newer versions of Access very easy. As a matter of fact, I had done the same thing a few years ago, and it turned out MS chose NOT to include a translator for some of the functionality I was using in 97. It required a complete rewrite to make it work in 2000.
I quickly discovered that I was not the only person in my organization that had this problem. There were many irate people here.
But in trying to give you suggestions, you might want to take a look at the references which are loaded with Access 2000 and compare them with the references your 97 version was using. Sometimes that's all you need to do to get things back on track.
Open a copy of the 97 db in Access97. Press Ctrl + g which will take you to the Visual Basic code screen having a lower window titled Immediate. (While you don't need that window, the Crtl + g method is a quick and dirty way of getting the VB code screen.)
On the menu bar select Tools, References. A small window will pop up listing all the references. Make note of all that are checked.
Now open the 2000 copy in A2K, and use the same method to get to the VB code window, and then the references window. First check if any of the references are marked as MISSING. If there are any, it means you need to browse thru your hard drive to try to locate them.
If there are any references from the 97 version that don't appear in the 2000 version, scroll down the references list until you find them and check them off. Hopefully this will correct your problem.
If it doesn't then you need to open in design mode, the forms containing the buttons. Select the button, and from its property sheet find out what its OnClick event code says. You may have to change the coding to point it in the right direction.
There are many threads throughout these forums discussing references. You might want to search them out to learn more about them.
HTH,
Vic
- Thread starter
- #3
- Status
Similar threads
- Locked
- Question
- Locked
- Question
- Locked
- Question
- Locked
- Question
