Alpha Software Mobile Development Tools:   Alpha Anywhere    |   Alpha TransForm subscribe to our YouTube Channel  Follow Us on LinkedIn  Follow Us on Twitter  Follow Us on Facebook
Devcon 2020 Goes Virtual! LEARN MORE >

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

QODBC and Runtime

Collapse
X
Collapse
 
  • Page of 1
  • Filter
  • Time
  • Show
Clear All
new posts
Previous template Next
    #1

    QODBC and Runtime

    I have an xbasic script that I use to update an SQL table based on info retrieved from QB using QODBC. I need to migrate this to my controller's machine, which has AA runtime. However, the permissions dialog doesn't open and so I cannot tell QB/QODBC that AA has permission. I suspect there is a difference between the runtime and the developer, but nothing I have tried has worked. Does anybody have any suggestions?
    Tags: None
    #2
    Re: QODBC and Runtime

    Originally posted by clafean View Post
    I have an xbasic script that I use to update an SQL table based on info retrieved from QB using QODBC. I need to migrate this to my controller's machine, which has AA runtime. However, the (QB?)permissions dialog doesn't open and so I cannot tell QB/QODBC that AA has permission. I suspect there is a difference between the runtime and the developer, but nothing I have tried has worked. Does anybody have any suggestions?
    No difference between runtime and developer for this.

    Are you logged in as Admin on QuickBooks?

    You need that the first time to get QB permission to outside programs.

    Is this the same version of QODBC on both machines or did you download a newer version for the controller's machine?
    Al Buchholz
    Bookwood Systems, LTD
    Weekly QReportBuilder Webinars Thursday 1 pm CST

    Occam's Razor - KISS
    Normalize till it hurts - De-normalize till it works.
    Advice offered and questions asked in the spirit of learning how to fish is better than someone giving you a fish.
    When we triage a problem it is much easier to read sample systems than to read a mind.
    "Make it as simple as possible, but not simpler."
    Albert Einstein

    http://www.iadn.com/images/media/iadn_member.png

    Comment

      #3
      Re: QODBC and Runtime

      Originally posted by Al Buchholz View Post
      No difference between runtime and developer for this.

      Are you logged in as Admin on QuickBooks? YES

      You need that the first time to get QB permission to outside programs. THIS HAPPENED

      Is this the same version of QODBC on both machines or did you download a newer version for the controller's machine?
      YES, THEY USE THE SAME VERSION.



      When I started working on my developer machine, I was getting the "access denied due to windows security" issue. I can't exactly remember what I had to do to make that go away, but whatever it was, I was able to authorize the connection one time and I was all set. I have managed to get her machine to authorize, but I still get the "access denied due to windows security" warning. Hmmmm.

      Comment

        #4
        Re: QODBC and Runtime

        I have no idea what that error is about. Do a Google search on that.

        report back with your findings. thank you.
        Al Buchholz
        Bookwood Systems, LTD
        Weekly QReportBuilder Webinars Thursday 1 pm CST

        Occam's Razor - KISS
        Normalize till it hurts - De-normalize till it works.
        Advice offered and questions asked in the spirit of learning how to fish is better than someone giving you a fish.
        When we triage a problem it is much easier to read sample systems than to read a mind.
        "Make it as simple as possible, but not simpler."
        Albert Einstein

        http://www.iadn.com/images/media/iadn_member.png

        Comment

          #5
          Re: QODBC and Runtime

          Apparently there is an issue with the UAC in Window 7/8; the connection administrator doesn't recognize that it is running as an Administrator sometimes. The QODBC documentation recommends running a query using the VB Demo that comes with it, and that will, in essence, force authorization. I did this and success! Thanks for your help, Al.

          Chuck

          Comment

            #6
            Re: QODBC and Runtime

            Originally posted by clafean View Post
            Apparently there is an issue with the UAC in Window 7/8; the connection administrator doesn't recognize that it is running as an Administrator sometimes. The QODBC documentation recommends running a query using the VB Demo that comes with it, and that will, in essence, force authorization. I did this and success! Thanks for your help, Al.

            Chuck
            Chuck

            Nice find.

            Gosh a problem because of UAC. Go figure.
            Al Buchholz
            Bookwood Systems, LTD
            Weekly QReportBuilder Webinars Thursday 1 pm CST

            Occam's Razor - KISS
            Normalize till it hurts - De-normalize till it works.
            Advice offered and questions asked in the spirit of learning how to fish is better than someone giving you a fish.
            When we triage a problem it is much easier to read sample systems than to read a mind.
            "Make it as simple as possible, but not simpler."
            Albert Einstein

            http://www.iadn.com/images/media/iadn_member.png

            Comment

            Previous template Next
            Working...
            X