Page 1 of 2 12 LastLast
Results 1 to 15 of 17
  1. #1
    4 Star Lounger
    Join Date
    Apr 2001
    Location
    Guatemala City
    Posts
    515
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Upgrade to XP (Win ME/Access 97)

    I will be upgrading programs from Access 97 to XP. Are there any words to the wise before I get started? I am modifying Dim statements to ..........As DAO.Recordset. To complicate matters, the XP will be the Spanish version, and I am expecting problems with date formats. Anything else that I should be aware of?

    Conversions always make me nervous, no matter how much I am told that the programs are compatible.

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

    Re: Upgrade to XP (Win ME/Access 97)

    Have a look at the thread beginning with <post#=211251>post 211251</post#> . It deals with the same question.
    Regards
    John



  3. #3
    Plutonium Lounger
    Join Date
    Dec 2000
    Location
    Sacramento, California, USA
    Posts
    16,775
    Thanks
    0
    Thanked 1 Time in 1 Post

    Re: Upgrade to XP (Win ME/Access 97)

    In addition to any version upgrade issues, you'll need to be sure that any dates and numbers passed into SQL statements are in US format. The number will give you the worst problem, since Spanish (at least the versions I've encountered) use a comma as the decimal delimiter and periods for digit grouping. If you try to pass a number like "2,5" into SQL or use it in DLookup, etc., you will get all sorts of nasty errors because SQL expects commas to separate members of a list. You should probably create a function to return a date string in US format for passing dates into SQL statements, and we did something similar for numbers in our applications. But it could be worse, some languages use spaces for digit grouping, and SQL *really* hates that! <img src=/S/grin.gif border=0 alt=grin width=15 height=15>

    Oh, another gotcha on internationalization, is that list separators may change. US/English format allows and understands commas, but for the other languages I've encountered, you need to use semicolons. That means, if you type in an Nz function with your regional settings set to Spanish, you have to type it as Nz([FieldName];0). Note the semicolon instead of a comma between the arguments. This is especially critical if you set the Master and Child Link fields for subforms and subreports from code. If you use a comma-delimited list of fields, non-US/English settings will ignore the fields. US settings are perfectly happy with the commas in the list of link fields, but they break in other settings.

    And if you develop in, say US English, and set field formats to things like "currency", "short date", "standard", etc., you will find that they convert to picture strings when you change to different regional settings. They don't change to the current regional format, they just change to format strings instead of the word you originally typed in. So if you want to see reports in Pesos, you can't just set the field format to "currency" unless you do it from code when you open the form or format the report. In that case, Access will understand that "currency" means whatever the current regional settings use.

    I've just gone through several weeks of finding all the possible problems switching between English (US) and Croation settings, so they're fresh in my mind.
    Charlotte

  4. #4
    4 Star Lounger
    Join Date
    Apr 2001
    Location
    Guatemala City
    Posts
    515
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Re: Upgrade to XP (Win ME/Access 97)

    It looks like the upgrade will be to Access 2000. Fewer problems? My home machine is Access 97. Will I be able to write stuff for the Access 2000 machine?

  5. #5
    Plutonium Lounger
    Join Date
    Dec 2000
    Location
    Sacramento, California, USA
    Posts
    16,775
    Thanks
    0
    Thanked 1 Time in 1 Post

    Re: Upgrade to XP (Win ME/Access 97)

    I'm not sure what you mean about fewer problems. If you're working in Access 97, you can only write Access 97 stuff. It can be opened in Access 2000 or converted to A2k format by Access 2000, but you won't be able to take advantage of a lot of features in Access 2000 using the approach.
    Charlotte

  6. #6
    4 Star Lounger
    Join Date
    Apr 2001
    Location
    Guatemala City
    Posts
    515
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Re: Upgrade to XP (Win ME/Access 97)

    <P ID="edit" class=small>(Edited by WendellB on 25-Jan-03 10:06. activate link to post)</P>I can't even get started on this conversion. I just get a message that it did not compile. Would it be an imposition on you all to take the stripped down data base that I sent up in my <post#=216846>post 216846</post#> and just see what happens when you try to convert it? If it does convert, then you could give me the settings in References. I really don't know where to begin.

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

    Re: Upgrade to XP (Win ME/Access 97)

    Unfortunately, we can't convert the database because you didn't include your system.mdw (or whatever the security file is called). I was however able to import all objects into a new XP database with no real difficulty, and get it to compile. So the problem you are having appears to be related to references. You can view references without trying to compile the database.
    Wendell

  8. #8
    4 Star Lounger
    Join Date
    Apr 2001
    Location
    Guatemala City
    Posts
    515
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Re: Upgrade to XP (Win ME/Access 97)

    OK. Could you pass me a list of the references that you have checked, please?

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

    Re: Upgrade to XP (Win ME/Access 97)

    It isn't possible to pass you a complete list, as I don't know what kind of controls you may be using, but among other things, you should almost certainly have a reference to Microsoft DAO 3.6 Object Library. In addition you should have references to VBA, MS Access 10.0 Object Library, and possibly to OLE Automation. Beyond that you could need references to many other things depending on what you are doing.
    Wendell

  10. #10
    5 Star Lounger
    Join Date
    Jul 2002
    Location
    Toronto, Ontario, Canada
    Posts
    1,139
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Re: Upgrade to XP (Win ME/Access 97)

    George,

    I don't have AXP, but I could open and convert the db to A2K.

    The only references I needed were:
    Visual Basic for Applications
    Microsoft Access 9.0 Object Library
    Microsoft DAO 3.6 Object Library
    OLE Automation


    I removed the reference to Microsoft Visual Basic for Applications Extensibility 5.3 and it still compiled fine. So if it isn't compiling for you, there is something else that was not included in the cut down db that is causing you problems.

    Although, you said that it just gives you a message saying that it couldn't be compiled. Usually along with that error, the VBE will highlight the line that is causing the problems.

    Maybe you could post that line, or look at the references and see if any are marked as Missing.
    --
    Bryan Carbonnell - Toronto <img src=/S/flags/Ontario.gif border=0 alt=Ontario width=30 height=18> <img src=/S/flags/Canada.gif border=0 alt=Canada width=30 height=18>
    Unfortunately common sense isn't so common!!
    Visit my website for useful Word, Excel and Access code, templates and Add-Ins

  11. #11
    Platinum Lounger
    Join Date
    Dec 2001
    Location
    Melbourne, Australia
    Posts
    4,594
    Thanks
    0
    Thanked 27 Times in 27 Posts

    Re: Upgrade to XP (Win ME/Access 97)

    Wendell, is there any reason you would go for DAO 3.6 as opposed DAO 3.5.1 for A97?
    Also Access 10.0 Object library should probably be Access 8 Object library, if not, can you explain why not.
    Pat

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

    Re: Upgrade to XP (Win ME/Access 97)

    Well I believe he is trying to upgrade from Access 97 to AccessXP/2002, so what I indicated were the references for AccessXP which is what I have.
    Wendell

  13. #13
    Platinum Lounger
    Join Date
    Dec 2001
    Location
    Melbourne, Australia
    Posts
    4,594
    Thanks
    0
    Thanked 27 Times in 27 Posts

    Re: Upgrade to XP (Win ME/Access 97)

    Thank you, I missed that, <img src=/S/doh.gif border=0 alt=doh width=15 height=15>

  14. #14
    4 Star Lounger
    Join Date
    Apr 2001
    Location
    Guatemala City
    Posts
    515
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Re: Upgrade to XP (Win ME/Access 97)

    There were some problems with the dates, but it looks like I am pretty well fixed. One strange thing - under Access 97 a particular form has the vertical scroll bar in place. When I go to 2002, the vertical scroll bar vanishes! So far, that is the only problem that remains. I don't have access to the machine yet except for short periods of time, so I don't know if other forms behave the same, or if there are other problems.

    How can I get that scroll bar back?

  15. #15
    Plutonium Lounger
    Join Date
    Dec 2000
    Location
    Sacramento, California, USA
    Posts
    16,775
    Thanks
    0
    Thanked 1 Time in 1 Post

    Re: Upgrade to XP (Win ME/Access 97)

    If you have the scrollbar set to vertical for the form, then it should show up in any version of Access. If you're working with scrollbars in subforms or controls, something else may be going on. Check to make sure you don't have any code that resets the scrollbar to 0.
    Charlotte

Page 1 of 2 12 LastLast

Posting Permissions

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