Results 1 to 11 of 11
  1. #1
    Join Date
    Feb 2008
    Location
    Fort Knox
    Posts
    32

    Question Unanswered: Access 2007 backwards compatability...

    I have actually developed my Access 2003 database without relationships in the tables in case Access 2007 did something different :P ... As a replacement I use the RunSQL macro and SQL commands to handle my Primary Key updating, deleting, ect... (like the UPDATE command) I'm wondering if Access 2007 will handle primary keys and relationships the same way as Access 2003?

    Also... I was turned on to the idea of using API functions by healdem. I found some nice VBScript code to get the full path to the database file (thanks to namliam) and I'm wanting to experiment with a way to do that using the Windows API.

    The only main guide-line I can think of is that I'm not sure if there will be any other instances of Access databases or applications running at the same time as my database.

    If someone has any experience with API and Access and could show me how to do this that would be great. I'm sorry to say yes I intend to just copy and paste, but I'll be using it to learn as well. I currently have only one example of API that my database application is currently using, so I don't have much to compare it to for learning just yet.

    On a side note, I'm wondering if Access 2007 still has it's own internal set of objects. The VBScript that namliam posted seems to use the basic Access libraries. If someone could let me know wether Access 2007 still has the same libraries then that would make me quite happy The specific function that I'm looking for is CurrentDb, and as far as I can tell, it is supposed to return the full path (including the file name) of the currently running database.

  2. #2
    Join Date
    Sep 2007
    Location
    Global Village
    Posts
    185
    Sorry Arkive but I cant undrestand what is your question?!! can you explain what exactly you want to do? Access 2007 supports all previous editions with primary key, API, SQL ....
    <<Never Walk on the Traveled Path, Because it only Leads you to where the Others have been.>>
    Graham Bell

  3. #3
    Join Date
    Feb 2008
    Location
    Fort Knox
    Posts
    32
    lol sorry Aran1, it was a 2 part question. The first part you answered (and thankyou)...

    The 2nd part I wasn't sure how to ask it, and I guess everyone could tell ... I'm trying to figure out how to extract the path to the database file using API. Another user on this forum showed me how to do that with VBScript... and now for flexability sake, I'm hoping to do it with API, and also because I'm wanting to learn.

    I've browsed the Windows API Reference, and it seems that the main funcion I'll need to use is GetCommandLine (as far as I can tell). However, after browsing over all the funcions that seemed pertinant to what I was looking for, it also seems that there really isn't a logical way to do that without using COM Objects. Aside from that, the process that I'll have to use is MSACCESS.EXE, and if multiple Access 2003 files are open, then how would I use GetCommandLine with MSACCESS.EXE to point to the right file?

    I guess my part 2 question is:

    Is there a way to retrieve the path to the currently active database file using API? And if so, would someone mind showing me a demonstration of that.

    I need this function because I won't know the full path to the database file on every computer network this database is used on. My database (if things go well) will be distributed to our offices all around the globe, so I can't hard code the path that I use into the functions and macros that I'll be creating.

    Is that a better way to word it?

  4. #4
    Join Date
    Dec 2004
    Location
    Madison, WI
    Posts
    3,926
    You can utilize the SystemInfo module (taken from the Access Developer's book by Sybex) in the attachment to get the mdb location/name (I put a function called GetMDBLocation as an example on the StartForm form.) If that's not what you're looking for, the SystemInfo has lots of other info you can return (just read the comments in the module.)
    Attached Files Attached Files
    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
    I don't understand why though, when VBA has things like CurrentProject.Path or similar.
    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
    Feb 2008
    Location
    Fort Knox
    Posts
    32

    Thanks!

    Thanks pkstormy... that actually confirms the way I'm doing it now, so... so far so good... And StarTrekker thanks for that little bit too... and for showing me another way to do that ... StarTrekker (on a slightly different topic) what would be the term to use to search the help for stuff like that? Or did you just go through the Object Browser one item at a time and click help and do a lot of reading?

    Has anyone else heard that Bill Gates is killing COM Objects? That rumor is why I am trying to do stuff with the Windows API instead of just relying on VBScript, VBA and Objects... That is also where my curiosity comes into play about Access 2007 backwards compatability. Aran1 already confirmed that backwards compatability should not be a problem.

    I'm just wondering if Access 2007 still has the Visiual Basic editor and the Object Browser with the same basic libraries/references. I'd just like to know if I will have to alter my code in the event my company upgrades. Will CurrentDb still be a usable function? Or will I have to find another function for Access 2007 to get my database to work the same?

    Can anyone who has Access 2007 confirm or deny that? (pretty please?) If I'm still not making sense I'm sorry, I don't know how else to explain it... but I can keep trying if someone is willing to still listen

    I've also heard of some Access 2003 database files not working properly in Access 2007. I really wonder what the big differences are, and what features/functions have been changed/updated...
    Last edited by TheArkive; 05-08-08 at 15:25.

  7. #7
    Join Date
    Nov 2007
    Location
    Adelaide, South Australia
    Posts
    4,049
    StarTrekker (on a slightly different topic) what would be the term to use to search the help for stuff like that? Or did you just go through the Object Browser one item at a time and click help and do a lot of reading?
    It's often a combination for me, necessity mixed with experience.

    Remember that there's lots of help out there when you search for things like "microsoft access" current database path in google too... don't limit your help searching to within Access!

    Has anyone else heard that Bill Gates is killing COM Objects?
    Not me.

    Aran1 already confirmed that backwards compatability should not be a problem.
    I'll confirm it too. Microsoft have always been pretty good with backwards compatibility.

    I'm just wondering if Access 2007 still has the Visiual Basic editor and the Object Browser with the same basic libraries/references. I'd just like to know if I will have to alter my code in the event my company upgrades.
    Yes it does. You may have to alter minor things to get older apps to function exactly as before, but nothing major.

    The biggest changes in Access 2007 are in the ribbon and in it's security.

    When I get back to my normal PC, I'll link you to a little review I did on Access 2007. It's a little negative, but should at least give you some idea on what has changed in 2007.

    CurrentDB is still there

    I've also heard of some Access 2003 database files not working properly in Access 2007.
    Never encountered this. Access 2007 runs all database files in 2000 format and up. If a 2003 database didn't work in Access 2007, it would have to be written pretty badly

    I really wonder what the big differences are, and what features/functions have been changed/updated...
    The big ones I know are:

    For 2000 - 2003 format files:
    You still have to use the native version to make changes to features not supported by 2007, such as menus, toolbars and security.

    For 2007 file format files:
    No Userlevel Security at all.
    The menu and toolbars are replaced with the ribbon and Quick Access Toolbar
    User interface is GREATLY altered.
    The Office Button cannot be hidden.
    The Ribbon cannot be hidden. It's contents can be customised with difficulty (XML)
    The Quick Access toolbar cannot be hidden. It can be customised though, to a point.

    They're the big ones I notice a lot.
    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

  8. #8
    Join Date
    Feb 2008
    Location
    Fort Knox
    Posts
    32
    Rock on, Thanks StarTrekker for the update ... that puts my mind at ease

  9. #9
    Join Date
    Sep 2007
    Location
    Global Village
    Posts
    185
    The Ribbon cannot be hidden. It's contents can be customised with difficulty (XML)
    The Ribbon can be hidden
    make a hidden table and name it USysRibbons with two fields, first one RibbonName and the oher one RibbonXml
    select a name for your ribbon and copy this xml in the RibbonXml and close the table
    Code:
    <customUI xmlns="http://schemas.microsoft.com/office/2006/01/customui"> 
       <ribbon startFromScratch="true">   </ribbon>
    
    </customUI>
    in access options select the ribbon name and next time you start the db you have no ribbon
    Cheers
    <<Never Walk on the Traveled Path, Because it only Leads you to where the Others have been.>>
    Graham Bell

  10. #10
    Join Date
    Nov 2007
    Location
    Adelaide, South Australia
    Posts
    4,049
    That's what I meant by "can be customised with difficulty". Previous versions handled customisation of toolbars and menus MUCH better.
    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

  11. #11
    Join Date
    Sep 2007
    Location
    Global Village
    Posts
    185
    Yes I agree its a pain in the neck customizing Ribbons in 2007
    <<Never Walk on the Traveled Path, Because it only Leads you to where the Others have been.>>
    Graham Bell

Posting Permissions

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