Page 1 of 2 12 LastLast
Results 1 to 15 of 19
  1. #1
    Join Date
    Mar 2008
    Posts
    1

    Unanswered: Access 2007 Migration

    Hello Everyone,

    My office is working with many large databases in Access 2003. Our instituion is requiring an "upgrade" to Access 2007, and there are many concerns about how the transfer will work and whether our databases will be corrupted.

    I was hoping to find out about some of the issues involving Access 2007, and how well it works with previous versions files. Is there anything specific we should be careful of when transfering our files?

    Or if someone could point me to any relevant threads on this forum, I would much appreciate it!

    Thanks,

    Tim

  2. #2
    Join Date
    Dec 2004
    Location
    Madison, WI
    Posts
    3,926
    When I've done upgrades, I'll usually take a glance at what's been changed in the new Access version (by googling "Changes in MS Access version 2007" or hit the Microsoft website). Then if there are any changes, specifically changes in code commands which are no longer there (which is rare and usually on non-standard code), I'll do a Find in the code (entire project) and see if that command is used somewhere in code.

    The biggest problems I've had with upgrades was activeX controls/references and I think once a class module I had imported from the web designed by someone. There was one idiotic Microsoft change in one Access version where they changed the activeX Calendar Control so the starting date (when converted), started on Monday when it had started on Sunday in the old version. I also had a few other activeX problems in upgrades (another I believe was the common dialog control.)

    The best advice I can give is to always test the new converted mdb on a test computer with JUST the new Access version installed (as I've also had some BIG problems when having 2 versions of Access on 1 computer - Microsoft has a note on having 2 versions of Access on 1 computer - but I'm not sure how applicable that is with 2003 and 2007.)

    I'd have a user test out the new version for a few months before you do a mass upgrade all at once. Otherwise you might find yourself staying late and into the morning making code fixes due to the upgrade. Upgrades simply should not be rushed unless it's absolutely necessary. But if there was any product I'd worry the least about in rushing for an upgrade, it'd probably be Access (although I had to do a quick upgrade from SQL Server 2000 to 2005 which took a whole 3 hours (including moving them to a new server) on 30+ databases and for the most part, it went flawlessly.)

    There shouldn't be any "corruption" issues unless bad code is written. Access is pretty good in regards to recovering from corruption problems and is pretty forgiving with code - even with upgrading to a new version of Access (crappy written code though can be problematic in any upgrade!) Keep in mind that like Access version 2002 (or 2003), you can probably still open previous versions of the mdb without actually converting the mdb (except a 97 version mdb). I'm not sure about opening a 2000 mdb with 2007 as I've only played with 2007 once or twice. I'm "guessing" though that 2007 will allow you to open all previous versions without converting except 97. I've yet to have any real serious problems opening up prior mdb versions with Access. (make sure to always compile the code!)

    Not sure what you mean by transferring our files unless you mean converting an mdb table from 2003 to 2007 which should happen flawlessly in the mdb conversion process (at least it has for me in working with all the previous versions of Access). Otherwise in regards to moving data from one mdb to another, my guess is it will work as previous versions where transferring data is as simple as linking a table into an mdb (or export/import) and then an append/update query or two.

    Sorry I can't be of more help. One of these days I'll get around to actually upgrading to 2007.
    Last edited by pkstormy; 03-17-08 at 23:08.
    Expert Database Programming
    MSAccess since 1.0, SQL Server since 6.5, Visual Basic (5.0, 6.0)

  3. #3
    Join Date
    Nov 2007
    Location
    Adelaide, South Australia
    Posts
    4,049
    My only advice here is to only "up"grade to 2007 if you absolutely have to. I hate the thing.
    Owner and Manager of
    CypherBYTE, Microsoft Access Development Specialists.
    Microsoft Access MCP.
    And all around nice guy!


    "Heck it's something understood by accountants ... so it can't be 'that' difficult..." -- Healdem
    "...teach a man to code and he'll be frustrated for life! " -- georgev

  4. #4
    Join Date
    Dec 2004
    Location
    Madison, WI
    Posts
    3,926
    StarTrekker - I wanted to ask, is 2007 Vista only? I remember using it on a Vista machine but I can't remember if it requires Vista.
    Expert Database Programming
    MSAccess since 1.0, SQL Server since 6.5, Visual Basic (5.0, 6.0)

  5. #5
    Join Date
    Nov 2007
    Location
    Adelaide, South Australia
    Posts
    4,049
    No, it runs on XP too. Not sure about versions prior to that as I don't have them anymore. Could look it up I suppose, but this will most likely answer your question
    Owner and Manager of
    CypherBYTE, Microsoft Access Development Specialists.
    Microsoft Access MCP.
    And all around nice guy!


    "Heck it's something understood by accountants ... so it can't be 'that' difficult..." -- Healdem
    "...teach a man to code and he'll be frustrated for life! " -- georgev

  6. #6
    Join Date
    Dec 2004
    Location
    Madison, WI
    Posts
    3,926
    I was too lazy to look it up and thought I'd just ask you since it sounds like you have more experience with it than my using it once or twice.

    I'm curious though why you hated it. I hated Vista but 2007 looked interesting.
    Expert Database Programming
    MSAccess since 1.0, SQL Server since 6.5, Visual Basic (5.0, 6.0)

  7. #7
    Join Date
    Sep 2007
    Location
    Global Village
    Posts
    185
    I'm using the 2007 version since it released, here is those problems that I can remember:
    1-if you use AciveX Calendar you can remove it as there is a built in calendar in 2007 version
    2-if you use a User Level Security in your dbs do not upgrade your db from mdb format to accdb format cuz 2007 version do not support user level security.
    3-regarding the 2000 version dbs which pkstormy noted I should say 2007 version can open 2000 mdb files.
    4-If you make a new 2007 accdb or upgrade your db to accdb format be informed that 2007 version doesn't support DAO method to access the other dbs, it can be used only with current project connection, you should use ADO to access to other dbs.
    Finally as pkstormy mentioned if you have some crappy codes in your db then you may or may not have problems which take time to debug and fix em.
    here is some new features for ver 2007 i got frm its help:
    --------------------------------------------------------------------------------

    New, improved user interface

    Great templates to get you started

    Enhanced sorting and filtering

    Layout view

    Stacked and tabular layouts

    Automatic calendar for date picking

    Rich text in memo fields

    Enhanced quick create by using the Create tab

    Create tables quickly by using the improved Datasheet view

    Total row in datasheets

    Field templates for creating new fields

    Field list task pane

    Split forms

    Multi valued fields

    Attachment data type for storing pictures, graphics, Office files, or any type of file

    Use an alternate background color

    Navigation Pane

    Embedded macros

    Improved Help viewer

  8. #8
    Join Date
    Dec 2004
    Location
    Madison, WI
    Posts
    3,926
    Aran1,

    Regarding 4 above...

    So 2007 doesn't support DAO that was writtin in prior versions?? I mean if you have an mdb written in DAO in 2000 or 2003 and convert it to 2007 or try to use it with 2007 (not converting it), will it work?

    That might make a lot of people unhappy if it doesn't as there are a LOT of DAO coders (I myself, prefer ADO over DAO).

    Or did I read you wrong Aran1 and are you talking about opening another mdb's linked tables via DAO only?
    Last edited by pkstormy; 03-18-08 at 03:08.
    Expert Database Programming
    MSAccess since 1.0, SQL Server since 6.5, Visual Basic (5.0, 6.0)

  9. #9
    Join Date
    Dec 2004
    Location
    Madison, WI
    Posts
    3,926
    The 3 things I read from Aran1's post which sound like a nice feature to have are:

    Rich text in memo fields

    Total row in datasheets

    Split forms

    (and the Multi valued fields sounds interesting)
    Last edited by pkstormy; 03-18-08 at 03:14.
    Expert Database Programming
    MSAccess since 1.0, SQL Server since 6.5, Visual Basic (5.0, 6.0)

  10. #10
    Join Date
    Sep 2007
    Location
    Global Village
    Posts
    185
    pkstormy,
    DAO feature only doesn't work if your db is 2007 format and you may want to connect to another db, but it works if you use it for current project connection.

  11. #11
    Join Date
    Nov 2007
    Location
    Adelaide, South Australia
    Posts
    4,049
    Quote Originally Posted by pkstormy
    I was too lazy to look it up and thought I'd just ask you since it sounds like you have more experience with it than my using it once or twice.

    I'm curious though why you hated it. I hated Vista but 2007 looked interesting.
    I hate Vista too, but only because of the plethora of applications and hardware that are not supported. I like the interface and other various upgrades. I had only one serious issue with it and it was related to network transfer speed under certain conditions. The network slowed to a crawl if you tried to copy a file of any significant size.

    As for Access 2007, here are the issues that make me hate it and you may be sorry you asked

    Inability to easily customise the ribbon.
    Huge backward step to be forced to "hack" system tables and have to write undocumented scripts of XML just to remove normal buttons. As for doing your own buttons with your own images it's even worse. Don't even think about turning it off. It can't be done.

    Inability to add custom built buttons to the Quick Access Toolbar.
    As far as I have found out so far, you cannot add your own customised buttons to this toolbar, only add the inbuilt ones.

    Inability to easily turn off customisation of the Quick Access Toolbar.
    If you could just switch off the customisation ability of this thing without having to remove every single ribbon tab, it would be much less of a security risk. As it is, any user can just add the design button to it, click that button and start hacking away at your work. Oh, and again, don't think of turning it off, because that can't be done either.

    Lack of support for any kind of menus.
    Basically, if you don't like the ribbon and simply want to use custom menus, tough luck. If you have an application with lots of custom menus and toolbars, you're gonna have to spend months re-developing. Existing custom menus of an upgraded application are buried in the Addins tab, making it look... well... unprofessional... until you've done the redevelopment work.

    Inability to remove the Office button.
    Developer applications will always look like 2007 applications and to be frank, that is an association I would rather not have.

    Lack of Security.
    Maybe User level security wasn't perfect, but together with good use of workgroups and MDE files, it was pretty much locked down. Now, you cannot lock down a database in the 2007 format. All that remains is MDE (ACCDE). It supports users and groups but they have no effect in a 2007 file format database.

    File sizes of applications bloat to a ridiculous extent. An 11MB ACCDE can grow to over a GIG within a month of normal usage. The exact same db in Access 97 never grew beyond 25MB. An absolute joke since you can't compact and repair an ACCDE and there is just no reason for it.

    The help system totally sucks now.
    You do a search for Format or whatever and you get 25 identical topics, one for each place and usage of "format" and you have to click them to find out what the difference is. Just a huge waste of time. To top it off, the content of these help files is once again, dumbed down for the garden variety user.

    Essentially, I get the impression that Microsoft have said "screw the developer, let's just focus on the garden variety user" and/or "hey we can make loads more money if we turn Access to sh*t and force the thousands of small developers to go down the .NET path".

    The only way to avoid these issues is to NOT upgrade to the 2007 file format and continue developing in Access 2003 or earlier and then just use Access 2007 to open its MDEs.

    Some improvements are good. I particularly like the alternate row formatting for continuous forms and reports and the fact that it supports MDEs of multiple previous versions

    /soapbox.
    Owner and Manager of
    CypherBYTE, Microsoft Access Development Specialists.
    Microsoft Access MCP.
    And all around nice guy!


    "Heck it's something understood by accountants ... so it can't be 'that' difficult..." -- Healdem
    "...teach a man to code and he'll be frustrated for life! " -- georgev

  12. #12
    Join Date
    Dec 2004
    Location
    Madison, WI
    Posts
    3,926
    Quote Originally Posted by StarTrekker
    I hate Vista too, but only because of the plethora of applications and hardware that are not supported. I like the interface and other various upgrades. I had only one serious issue with it and it was related to network transfer speed under certain conditions. The network slowed to a crawl if you tried to copy a file of any significant size.
    The biggest problem I had with Vista (other than it was a memory hog) was that on my wireless network (I have 6 computers connected on my home network), I had to install LLTD on the XP boxes in order for Vista to see my XP computers over the network and vice-versa (which took me a while to research but was fairly easy once I discovered the problem).

    Thanks for all the info on Access 2007 StarTrekker! Greatly appreciated.
    Last edited by pkstormy; 03-18-08 at 14:49.
    Expert Database Programming
    MSAccess since 1.0, SQL Server since 6.5, Visual Basic (5.0, 6.0)

  13. #13
    Join Date
    Nov 2007
    Location
    Adelaide, South Australia
    Posts
    4,049
    You're most welcome
    Owner and Manager of
    CypherBYTE, Microsoft Access Development Specialists.
    Microsoft Access MCP.
    And all around nice guy!


    "Heck it's something understood by accountants ... so it can't be 'that' difficult..." -- Healdem
    "...teach a man to code and he'll be frustrated for life! " -- georgev

  14. #14
    Join Date
    Nov 2007
    Location
    Adelaide, South Australia
    Posts
    4,049
    Argggggghghhhhhhhhhhhhhhh!!!

    See what I mean about the stupid bleepin' help now... Put your cursor in a DisplayWhen property and press F1. If you really need help on it, say goodbye to the next 15 mins just to find the specific bit of help you're after. I am trying to make graphics print in greyscale, but still show on screen in colour and I think DisplayWhen is my only hope.
    Attached Thumbnails Attached Thumbnails sshot.jpg  
    Last edited by StarTrekker; 03-19-08 at 04:16.
    Owner and Manager of
    CypherBYTE, Microsoft Access Development Specialists.
    Microsoft Access MCP.
    And all around nice guy!


    "Heck it's something understood by accountants ... so it can't be 'that' difficult..." -- Healdem
    "...teach a man to code and he'll be frustrated for life! " -- georgev

  15. #15
    Join Date
    Dec 2002
    Location
    Préverenges, Switzerland
    Posts
    3,740
    #11 triggered something that has been building for a few months - i have decided that i will not tolerate A07. as a consequence, i now need to learn a new way to talk to data.

    any volunteers with suggestions for a decent replacement language/environment ?

    izy
    currently using SS 2008R2

Posting Permissions

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