locked
MS Access 2 vs MS Access 2010 RRS feed

  • Question

  •  

    Hi

    Im a Unix C++ programmer who has been asked to do some dev work on an old Access 2 database.  I don't have time to wade thru the manuals of a 2 decade old application, so please help me!

    Ive got the Access 2 application which has a bunch of database files, sql queries, macros etc.  I can open this in Access 2.  If I set the paths correctly in a file called PAS.INI, and run a binary called PAS.EXE I get the application GUI and all works fine.

    I converted the database file to Access 2003, then imported that into Access 2010. Again, all looks fine.

    What I don't get, is

    a) what does PAS.EXE actually run?  Is PAS.EXE the access 2 runtime, or a compiled set of database macros, GUI stuff etc?

    b) What do I need to do to run the whole system in Access 10 like I can in Access 2?

    I hope that makes sense?

    Thanks


    Duncan Kerr

    Tuesday, March 6, 2012 8:55 AM

Answers

  • Makes sense, but that's not what the runtime does.

    Packaging an Access application with the runtime doesn't change the application in any way, shape or form. All it does is create a package that also includes a version of msaccess.exe that's "crippled" through literally hundreds of registry entries so that it can only be used to update data, not make any design changes.

    An .accdc file is simply a digitally-signed version of the .accdb file.


    Doug Steele, Microsoft Access MVP
    http://www.AccessMVP.com/djsteele (no e-mails, please!)
    Co-author Access Solutions — Tips, Tricks, and Secrets from Microsoft Access MVPs (ISBN 978-0-470-59168-0)

    • Marked as answer by Bruce Song Wednesday, April 4, 2012 3:14 AM
    Thursday, March 8, 2012 11:51 AM

All replies

  • I can't tell you what Pas.exe is - might be a custom exe?

    To allow the Access 2010 to run as the Access 2 app you can either use the build-in Package Installer wizard (File -> Save & Publish -> Package Solution) or use a third party app like SageKey.

    Tuesday, March 6, 2012 10:00 AM
  • PAS.EXE is definitely not the Access 2.0 runtime. I can't remember what it was called, but it started with ms. While it's possible someone could have renamed the executable, I believe it used MSACCESS.INI, not PAS.INI


    Doug Steele, Microsoft Access MVP
    http://www.AccessMVP.com/djsteele (no e-mails, please!)
    Co-author Access Solutions — Tips, Tricks, and Secrets from Microsoft Access MVPs (ISBN 978-0-470-59168-0)

    Tuesday, March 6, 2012 12:33 PM
  • PAS.EXE is definitely not the Access 2.0 runtime. I can't remember what it was called, but it started with ms. While it's possible someone could have renamed the executable, I believe it used MSACCESS.INI, not PAS.INI


    Doug Steele, Microsoft Access MVP
    http://www.AccessMVP.com/djsteele (no e-mails, please!)
    Co-author Access Solutions — Tips, Tricks, and Secrets from Microsoft Access MVPs (ISBN 978-0-470-59168-0)

    Tuesday, March 6, 2012 12:33 PM
  • FYI the Access 2.0 runtime was named MSARN200.EXE.
    Tuesday, March 6, 2012 12:54 PM
  • OK, so I packaged and signed the database, but that doesnt give me the runtime applcation.  I get a .accdc file.  what Im trying to do is to get Access 2010 generate an exe which will run my database, menus etc.

    Make sense?


    Duncan Kerr

    Thursday, March 8, 2012 6:16 AM
  • Makes sense, but that's not what the runtime does.

    Packaging an Access application with the runtime doesn't change the application in any way, shape or form. All it does is create a package that also includes a version of msaccess.exe that's "crippled" through literally hundreds of registry entries so that it can only be used to update data, not make any design changes.

    An .accdc file is simply a digitally-signed version of the .accdb file.


    Doug Steele, Microsoft Access MVP
    http://www.AccessMVP.com/djsteele (no e-mails, please!)
    Co-author Access Solutions — Tips, Tricks, and Secrets from Microsoft Access MVPs (ISBN 978-0-470-59168-0)

    • Marked as answer by Bruce Song Wednesday, April 4, 2012 3:14 AM
    Thursday, March 8, 2012 11:51 AM
  • Makes sense, but that's not what the runtime does.

    Packaging an Access application with the runtime doesn't change the application in any way, shape or form. All it does is create a package that also includes a version of msaccess.exe that's "crippled" through literally hundreds of registry entries so that it can only be used to update data, not make any design changes.

    An .accdc file is simply a digitally-signed version of the .accdb file.


    Doug Steele, Microsoft Access MVP
    http://www.AccessMVP.com/djsteele (no e-mails, please!)
    Co-author Access Solutions — Tips, Tricks, and Secrets from Microsoft Access MVPs (ISBN 978-0-470-59168-0)

    Thursday, March 8, 2012 11:51 AM