If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. |
|
|
|
Thread Tools | Display Modes |
#11
|
|||
|
|||
SOLUTION: Running Access 2003 db in 2007, and a few forms don't work
I wanted to post back in case anyone else is pursuing similar issues. This
is an issue with either checking a form into Visual SourceSafe or checking it back out. I had 3 out of 20 or so forms in an Access 2003 db that would not open in Access 2007. All 3 were resolved by removing the hotkeys assigned to controls and/or tab pages. One of them was a very simple form, based on a single table with about 10 fields. All my forms have a find-a-row combo box in the form header, with AltF assigned as the hotkey by setting the label caption to "&Find:". Removing that ampersand fixed the problem. Some of the other problem forms needed additional hotkeys removed. Every one of my forms has the same setup. All but those 3 work fine with the hotkeys. "Allen Browne" wrote in message ... Paul, I don't use VSS, so can't really provide you with info on that. Perhaps someone who uses it can comment. -- Allen Browne - Microsoft MVP. Perth, Western Australia Tips for Access users - http://allenbrowne.com/tips.html Reply to group, rather than allenbrowne at mvps dot org. "Paul Shapiro" wrote in message ... OK, I thought everything was clean, but it's not finished yet. I checked everything out from SourceSafe. I removed the code modules from the 3 problematic forms that weren't opening in Access 2007 (out of memory error). I decompiled the db, successfully, and then compacted/repaired. I re-created the code modules for those 3 forms. I checked everything back into SourceSafe. At this point the db worked fine in Access 2007. Before distributing a db, I like to create a new db from SourceSafe, so I did that. That db has the original problem (out of memory error) with the same 3 forms. So it looks like either checking objects into SourceSafe or generating objects from SourceSafe is causing the problem. Any more suggestions? Is this something that might be worth pursuing with Microsoft Support? I get a free support incident via MSDN so it doesn't cost money, I think. |
#12
|
|||
|
|||
SOLUTION: Running Access 2003 db in 2007, and a few forms don't work
On Fri, 22 Jun 2007 12:30:10 -0400, "Paul Shapiro"
wrote: All 3 were resolved by removing the hotkeys assigned to controls and/or tab pages. VERRY interesting. Thanks Paul, I'll try to remember this! John W. Vinson [MVP] |
#13
|
|||
|
|||
SOLUTION: Running Access 2003 db in 2007, and a few forms don't work
Thanks for posting the solution, Paul.
I never would have guessed VSS would barf over the hotkeys. Hopefully that will help someone else in future as well. -- Allen Browne - Microsoft MVP. Perth, Western Australia Tips for Access users - http://allenbrowne.com/tips.html Reply to group, rather than allenbrowne at mvps dot org. "Paul Shapiro" wrote in message ... I wanted to post back in case anyone else is pursuing similar issues. This is an issue with either checking a form into Visual SourceSafe or checking it back out. I had 3 out of 20 or so forms in an Access 2003 db that would not open in Access 2007. All 3 were resolved by removing the hotkeys assigned to controls and/or tab pages. One of them was a very simple form, based on a single table with about 10 fields. All my forms have a find-a-row combo box in the form header, with AltF assigned as the hotkey by setting the label caption to "&Find:". Removing that ampersand fixed the problem. Some of the other problem forms needed additional hotkeys removed. Every one of my forms has the same setup. All but those 3 work fine with the hotkeys. |
|
Thread Tools | |
Display Modes | |
|
|