Results 1 to 13 of 13
  1. #1
    4 Star Lounger
    Join Date
    Feb 2001
    Location
    Richland, Washington, USA
    Posts
    407
    Thanks
    0
    Thanked 0 Times in 0 Posts

    2003 to 2007 Conversion (2007 / 2003)

    I am JUST BEGINNING the process of testing the use of a production Access database (Front-End on client, Back-End on server) using Office 2007 (the application was developed using Access 2003). For starters, I'd like to just run the application as an mdb (2002-2003) format database (not the new 2007 format) as some users will continue to use Office 2003 for a while, while others start migrating to Office 2007. My understanding is that there should be no (!) compatibility issues with some front-ends running from Office 2007 while others are running frim Office 2003 (both accessing the shared back-end on the server). Is there anything I should be aware of (or reference sources on the web) as I jump into this?

    In the first "poof-testing", things seem to behave fairly well. One annoyance, though -- for one of the custom toolbars used by the application, I cloned the "Close" menu item from the built-in menu (when the application was developed in Access 2003) -- in Access 2007, this button doesn't work (it's in a custom toolbar supporting Print Preview). Is there something systematic here that I should be aware of. Otherwise (so far), the custom menus work okay. Related to this, does Access 2007 have an interface for customizing toolbars & custom menus for backwards compatibility? Someday, I'll convert the whole beast to the new Access 2007 format and convert the menus/toolbars to ribbons... someday, but not until everybody's off Access 2003!

    Thanks,

  2. #2
    Plutonium Lounger
    Join Date
    Mar 2002
    Posts
    84,353
    Thanks
    0
    Thanked 29 Times in 29 Posts

    Re: 2003 to 2007 Conversion (2007 / 2003)

    Access 2007 can work with databases in Access 2000 or Access 2002/2003 format without conversion.

    Since the entire menu/toolbar structure has been overhauled in Access 2007, you shouldn't use built-in buttons on your custom toolbars. Create custom functions or macros for the actions they represented, and then create custom buttons that execute these functions or macros.

    I hope others will have first-hand tips (I don't have Office 2007 myself).

  3. #3
    Super Moderator
    Join Date
    Jun 2002
    Location
    Mt Macedon, Victoria, Australia
    Posts
    3,993
    Thanks
    1
    Thanked 45 Times in 44 Posts

    Re: 2003 to 2007 Conversion (2007 / 2003)

    I am in much the same situation as you. I work in 2003, and I have lots of databases in 2000 format , but various users are starting to use 2007 (some with Vista).

    So I have a separate computer with Vista and 2007 that I use for testing, but by and large I still do all the work in 2003. I will get References problems if I work on the db in 2007 then give it to a 2003 user.

    While things seem to work OK, I recently had one slab of code that did not work on 2007. I could not see anything wrong with it, and it worked ok in 2003, but 2007 users all got the same error.

    Some things might run more slowly in 2007. I had a procedure for finding the location of the backend that was a bit longwinded. On some 2007 machines it never seemed to get to the end, so I had replace the whole function with a faster one.

    So just because most things seem to work, don 't assume that everything will.

    I am not sure whether you are looking at Vista at the same time. On Vista machines, any other programmes you call may be in a different location.

    On an XP machine this will find Irfanview

    If Dir("C:Program FilesIrfanViewi_view32.exe") <> "" Then

    On Vista it needs to be:
    If Dir("C:Program Files (x86)IrfanViewi_view32.exe") <> "" Then
    Regards
    John



  4. #4
    4 Star Lounger
    Join Date
    Feb 2001
    Location
    Richland, Washington, USA
    Posts
    407
    Thanks
    0
    Thanked 0 Times in 0 Posts

    2003 to 2007 Conversion Woes

    Okay, here's another peculiarity that maybe someone's seen or can explain, or (better yet) can tell me how to fix!

    I have a custom menu (Command Bar) that I configure during start-up based on the user's permissions / access level. This works fine in Access 2003. When I try to run it in Access 2007 the configuration based on the user doesn't happen during startup (I get the menu the way it was configured last via Access 2003 or manually via Access 2007 -- see just ahead). If I open the application bypassing the startup code to get the Access 2007 user interface and then run the startup code manually, the custom menu gets set up properly but, of course, its in the Add-Ins tab as a Custom Toolbar. As long as I have both 2003 and 2007 users, I want (need) to retain the 2003 look-and-feel for this application, so I need to figure out a way to get this menu to get configured properly on start-up in Access 2007. Does anyone have an idea why it's not?

    Thanks.

  5. #5
    Silver Lounger
    Join Date
    Jun 2001
    Location
    Niagara Falls, New York, USA
    Posts
    1,878
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Re: 2003 to 2007 Conversion Woes

    Hi Tom

    Can you share with us how you got your Custom Toolbar to work in 2007?

    Thanks, John

  6. #6
    Super Moderator
    Join Date
    Aug 2001
    Location
    Evergreen, CO, USA
    Posts
    6,624
    Thanks
    3
    Thanked 60 Times in 60 Posts

    Re: 2003 to 2007 Conversion Woes

    Wendell

  7. #7
    Silver Lounger
    Join Date
    Jun 2001
    Location
    Niagara Falls, New York, USA
    Posts
    1,878
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Re: 2003 to 2007 Conversion Woes

    Thanks for the links, they were very helpful

    This is my first experience with 2007, on the surface it seems to be quite a new learning expericece.

    Is there a classic GUI for Office 2007?

    What has the end user acceptance been for Office 2007?

    In the pass when I make even the slightest change to an application it takes much time for for acceptance in most cases.

    John

  8. #8
    Plutonium Lounger
    Join Date
    Mar 2002
    Posts
    84,353
    Thanks
    0
    Thanked 29 Times in 29 Posts

    Re: 2003 to 2007 Conversion Woes

    Microsoft itself doesn't offer a classic interface. See <post:=745,217>post 745,217</post:> for some ways to emulate the menu/toolbar interface in Office 2007.

    But users should get used to it - the ribbon isn't going to go away. The first screenshots of the next version of Office show that Microsoft won't revert to the classic interface.

  9. #9
    4 Star Lounger SteveH's Avatar
    Join Date
    Jan 2001
    Location
    Chelsea, Gtr London, United Kingdom
    Posts
    587
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Re: 2003 to 2007 Conversion (2007 / 2003)

    <hr>, I cloned the "Close" menu item from the built-in menu (when the application was developed in Access 2003) -- in Access 2007, this button doesn't work (it's in a custom toolbar supporting Print Preview). <hr>

    I have the same scenario (App is a A2K mde front-end with A2K back-end running mainly on O2007) This Close button issue is a known bug http://allenbrowne.com/Access2007.html .
    Steve H
    IT Lecturer/Access Developer
    O2K SR3/O2010; Win7Pro

  10. #10
    Silver Lounger
    Join Date
    Jun 2001
    Location
    Niagara Falls, New York, USA
    Posts
    1,878
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Re: 2003 to 2007 Conversion Woes

    The links were very helpful!

    Most of the links refer to Access 2003, do I assume they will work with Access 2000?

    Thanks, John

  11. #11
    Plutonium Lounger
    Join Date
    Mar 2002
    Posts
    84,353
    Thanks
    0
    Thanked 29 Times in 29 Posts

    Re: 2003 to 2007 Conversion Woes

    Those add-ins work with Office 2007 to emulate the Office 2003 interface. They don't work in Access 2003, 2002 or 2000!

    And as far as I know there is no add-in to make Access 2007 look like Access 2000, but then the difference between Access 2000, 2002 and 2003 isn't great.

  12. #12
    4 Star Lounger
    Join Date
    Feb 2001
    Location
    Richland, Washington, USA
    Posts
    407
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Re: 2003 to 2007 Conversion Woes

    John,

    Sorry to be so slow in getting back to you; obviously other Loungers have come to your rescue!

    Here's a brief accounting of my experience with the Access 2003 to 2007 transition (so far):

    For my applications, we still have a mix of 2003 (less and less) and 2007 (more and more) users (who need access to the same database). To MS's credit, this has been surprisingly painless. Of course, you have to retain the 2003 database format (.mdb) which 2007 handles satisfactorily. If you have a "buttoned-up" application (custom menu bar, database window inaccessible, etc.), Access 2007 will open the database in near 2003-look-alike format (your menu only, no ribbons, etc.). There are a few annoyances -- macro/VBA security has to be dealt with when opening the database (which can be foreign to the users) -- this can be dealt with by setting up trusted sites. The dead close button mentioned in this thread is annoying (I haven't looked yet at some of the resources Wendell and Hans have suggested). On forms with list boxes, the highlighted list box entry tends to only be outlined rather than highlighted with a different background color, but this may have something to do with my VBA coding behind the form -- but it does behave differently than 2003 which is an annoyance. I do use user-level security for some of my databases which works fine (again, I have retained the .mdb database format for backwards compatibility).

    I have started doing development work on the .mdb databases in Access 2007, and haven't encountered any significant problems (the biggest hurdle is getting used to the new interface); there seem to be lots of new form/control/report properties -- I'm leary of how these will work for those remaining Access 2003 users, so I am avoiding them for now. Fortunately, the VBA Editor has retained it's "classic" format, so there is no learning curve there. The biggest challenge may well be maintaining/ revising my custom menus (I haven't had to deal with this yet using Access 2007) as Access 2007 does not have an interface for customizing menus and toolbars. They have to be maintained using VBA/Macros as described in some of the links provided by other loungers in this thread.

    Once everyone is off Access 2003, it will probably make sense to bite the bullet and convert the menus/toolbars to ribbons (another learning curve, particularly since some of my applications dynamically change the content in the menus), revamp the user-level security to fit the security philosophy behind Access 2007 (I'm still ignorant on this -- any good resources out there?) as user accounts/user permissions are absent from the new .accdb database format (as I understand it). It will also make sense to convert the .mdb up to .accdb (which may have to be done anyway to accommodate some of the above changes) and then deal with any other inconsistencies between the two formats. I guess I would rather spend my time adding to the capabilities of my applications, but I guess we have to move on. Of course, Access 2007 may well enable additional capabilities (e.g., RTF format for text/memo fields) that wouldn't be possible (or at least as easy) in Access 2003. Keeps life interesting...

    Regards,

  13. #13
    Silver Lounger
    Join Date
    Jun 2001
    Location
    Niagara Falls, New York, USA
    Posts
    1,878
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Re: 2003 to 2007 Conversion Woes

    Hi Tom

    Thanks for the update, it was very helpful and confirms things that i have stumbled on.

    When you get a chance could you review <post#=757756>post 757756</post#>

    Access 2007 Opening FE.mdb the first time? (A2007 (12.0.6334.5000) SP1 Jet 4.0 SP-8)

    Specifically - When I open the Access 2000 FE.mdb the first time with Access 2007 it taks 7 minutes to open

    If you have something to contribute please do it on <post#=757756>post 757756</post#>

    Thanks, John

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •