Announcement

Collapse

The Alpha Software Forum Participation Guidelines

The Alpha Software Forum is a free forum created for Alpha Software Developer Community to ask for help, exchange ideas, and share solutions. Alpha Software strives to create an environment where all members of the community can feel safe to participate. In order to ensure the Alpha Software Forum is a place where all feel welcome, forum participants are expected to behave as follows:
  • Be professional in your conduct
  • Be kind to others
  • Be constructive when giving feedback
  • Be open to new ideas and suggestions
  • Stay on topic


Be sure all comments and threads you post are respectful. Posts that contain any of the following content will be considered a violation of your agreement as a member of the Alpha Software Forum Community and will be moderated:
  • Spam.
  • Vulgar language.
  • Quotes from private conversations without permission, including pricing and other sales related discussions.
  • Personal attacks, insults, or subtle put-downs.
  • Harassment, bullying, threatening, mocking, shaming, or deriding anyone.
  • Sexist, racist, homophobic, transphobic, ableist, or otherwise discriminatory jokes and language.
  • Sexually explicit or violent material, links, or language.
  • Pirated, hacked, or copyright-infringing material.
  • Encouraging of others to engage in the above behaviors.


If a thread or post is found to contain any of the content outlined above, a moderator may choose to take one of the following actions:
  • Remove the Post or Thread - the content is removed from the forum.
  • Place the User in Moderation - all posts and new threads must be approved by a moderator before they are posted.
  • Temporarily Ban the User - user is banned from forum for a period of time.
  • Permanently Ban the User - user is permanently banned from the forum.


Moderators may also rename posts and threads if they are too generic or do not property reflect the content.

Moderators may move threads if they have been posted in the incorrect forum.

Threads/Posts questioning specific moderator decisions or actions (such as "why was a user banned?") are not allowed and will be removed.

The owners of Alpha Software Corporation (Forum Owner) reserve the right to remove, edit, move, or close any thread for any reason; or ban any forum member without notice, reason, or explanation.

Community members are encouraged to click the "Report Post" icon in the lower left of a given post if they feel the post is in violation of the rules. This will alert the Moderators to take a look.

Alpha Software Corporation may amend the guidelines from time to time and may also vary the procedures it sets out where appropriate in a particular case. Your agreement to comply with the guidelines will be deemed agreement to any changes to it.



Bonus TIPS for Successful Posting

Try a Search First
It is highly recommended that a Search be done on your topic before posting, as many questions have been answered in prior posts. As with any search engine, the shorter the search term, the more "hits" will be returned, but the more specific the search term is, the greater the relevance of those "hits". Searching for "table" might well return every message on the board while "tablesum" would greatly restrict the number of messages returned.

When you do post
First, make sure you are posting your question in the correct forum. For example, if you post an issue regarding Desktop applications on the Mobile & Browser Applications board , not only will your question not be seen by the appropriate audience, it may also be removed or relocated.

The more detail you provide about your problem or question, the more likely someone is to understand your request and be able to help. A sample database with a minimum of records (and its support files, zipped together) will make it much easier to diagnose issues with your application. Screen shots of error messages are especially helpful.

When explaining how to reproduce your problem, please be as detailed as possible. Describe every step, click-by-click and keypress-by-keypress. Otherwise when others try to duplicate your problem, they may do something slightly different and end up with different results.

A note about attachments
You may only attach one file to each message. Attachment file size is limited to 2MB. If you need to include several files, you may do so by zipping them into a single archive.

If you forgot to attach your files to your post, please do NOT create a new thread. Instead, reply to your original message and attach the file there.

When attaching screen shots, it is best to attach an image file (.BMP, .JPG, .GIF, .PNG, etc.) or a zip file of several images, as opposed to a Word document containing the screen shots. Because Word documents are prone to viruses, many message board users will not open your Word file, therefore limiting their ability to help you.

Similarly, if you are uploading a zipped archive, you should simply create a .ZIP file and not a self-extracting .EXE as many users will not run your EXE file.
See more
See less

Problem with Displaying Access Table data using ADO/ODBC

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • Problem with Displaying Access Table data using ADO/ODBC

    Firstly, I have to say that this is probably just past the scope of my programming knowledge.
    I have two tables in an access MDB that I wish to display , using the "display ASO/ODBC data in a Form" genie.
    One table has a primary key defined, the second does not.
    I can use all the functions on the first table (one with primary key) but none of the functions work in the non-primary key table.
    I get variations on the message

    OLE Automation Error. Sources is ADODB.Recordset
    Operation is not allowed when Object is closed.
    Recordset.absoluteposition subelement not found.
    what do I have to define in the genie to overcome this problem. (this is the more important of the two tables to display !!).

    thanks
    Last edited by Graham Wickens; 08-04-2019, 05:11 AM. Reason: spelling
    --
    Support your local Search and Rescue Unit, Get Lost!

    www.westrowops.co.uk

  • #2
    Re: Problem with Displaying Access Table data using ADO/ODBC

    Create a PK in the other table.
    Without a PK, you can't do much more than read the table sequentially.
    You need a key to carry out processing operations.
    Same with SQL.
    Ted Giles
    Example Consulting - UK
    .

    sigpichttp://ec12.example-software.com//
    See our site for Alpha Support, Conversion and Upgrade.

    Comment


    • #3
      Re: Problem with Displaying Access Table data using ADO/ODBC

      Love the first Sentence, Never used Access other than to read data
      --
      Support your local Search and Rescue Unit, Get Lost!

      www.westrowops.co.uk

      Comment


      • #4
        Re: Problem with Displaying Access Table data using ADO/ODBC

        Looking into this a little deeper, the two access tables are connected in a "one-to-many" link on the "Keyno" field.
        "Genav" is the Main table and "Genav_Index" is the child.
        Presumably I have to SELECT fields to build each combined record to display, something along the lines ...


        SELECT [CurrentID], [ACtype], [Series], [Code], [Con], [LineNum], [[Home_Airfield], [ [KeyNo] FROM [genav]
        SELECT [Current], [Reg], [Pi_Sort] FROM [genav_index] WHERE [genav_index.Keyno] = [genav.keyno]
        As yet I am still trying to find the correct syntax (by trial and error on my part).

        Looking at the xbasic from the ADO Genie, it would appear that I have to define a "DataObj" for both tables.
        I also presume there will be more horrors awaiting me as I scroll through the xbasic!

        I have got it working in A5, but each time the access DB is updated, I have to import the two tables into A5 from access, change the keyid to a character field and build the one-to-many set. This is very time consuming as the combined number of records is nearly 2 million !!

        I should add that I will only ever be reading from the access tables.

        I am both the Developer and the User, so it is an overhead I could really do without (in terms of time and brain).

        My theory is that this should be possible as both Access and A5 know about one-to-many links (terminology is different) and I am presuming that ADO/ODBC can also cope with one-to-many as well?
        Last edited by Graham Wickens; 08-05-2019, 10:12 AM. Reason: Additional Information
        --
        Support your local Search and Rescue Unit, Get Lost!

        www.westrowops.co.uk

        Comment


        • #5
          Re: Problem with Displaying Access Table data using ADO/ODBC

          Have you tried converting the Access database to Excel? Then you should be able to save the XLS as DBF.
          Robin

          Discernment is not needed in things that differ, but in those things that appear to be the same. - Miles Sanford

          Comment

          Working...
          X