Results 1 to 4 of 4
  1. #1
    Arabesque
    Guest

    Porting (Win 3.1)

    I am attempting to port an Access 2 application to Access 2000. What's a good start to figuring out what to do about changing existing code from 16 to 32 bit.

  2. #2
    Linda616
    Guest

    Re: Porting (Win 3.1)

    Thank you, I have attempted that already. I even upgraded to Win 95 (and used Access 97) to preserve 16 bit functionality, but still get error messages of references to 16 bit calls. As you say, some commands are not valid anymore and thank you for the tip about Access Basic.

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

    Re: Porting (Win 3.1)

    You would be best advised to upgrade it to Access 95 or 97 first. Access 2.0 used Access Basic rather than VBA, so there are significant differences in the code. But you can't run Office 2000 on Win 3.1, if that's what you're trying to do.
    Charlotte

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

    Re: Porting (Win 3.1)

    The 32-bit Win API has a bunch of renamed elements and a large number of new ones. Even some of the same name calls have different argument types from the 16-bit version. Are your errors occurring in the actual API calls or in pure Access code?
    Charlotte

Posting Permissions

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