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

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, QBES8, AlphaFive V6 integration

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

    QODBC, QBES8, AlphaFive V6 integration

    I have an AlphaFiveV6 app using QODBC Enterprise Edition and QBES 8 for server. This app (reads data from QB) was working fine with QODBC Full Version, QBES 6 until the client upgraded his QB POS to the lastest version. Then the ADO commands to read data from QuickBooks stopped working.

    The QODBC Test Connection works, the QODBC VB Demo works and even the ODBC Import Genie in Alpha Five works, but when I copy the import genie Xbasic code to a script file and run the script file, it doesn't work.

    At first I thought the QODBC driver was somehow corrupt, because the app worked fine on my computer at home. But QODBC support said it's fine.

    Since the app stopped working, I went ahead and allowed the client to upgrade his QBES 6 to 8 and we installed the correct QODBC Enterprise Edition. The problem remains though. Then I was thinking AlphaFive somehow became corrupted, until I did further testing on my computer at home. I also upgraded to QBES 8 for SERVER. Now my app doesn't work either. Although I don't have QBPOS installed, I'm now wondering if it has something to do with the server versions of QBES and QBPOS.

    I created 2 trace files - one running odbc_import_table from the import genie, the second running the same command from a script file. I've included the second so you see where the program stops working (although the program never ends, it just hangs and I have to end the process).

    The following is the code that works from the import genie, but not from a script:
    odbc_import_table("ODBC","QuickBooks Data","C:\Documents And Settings\Doublej\My Documents\Instrument Rental Application\qb customers2.dbf","SELECT * FROM CUSTOMER","","")

    The following is the trace file when the program doesn't work:
    ISAMOpen
    Database: .
    DSN: QuickBooks Data
    UserName:
    Password:
    DeveloperCode:
    ApplicationCode:
    OpenMode: F
    UseDCOM: N
    IBizRemoteConnection: N
    IBizRemoteURL: http://localhost:2080
    IBizRemoteUserName: admin
    IBizRemotePassword:
    IBizRemoteAskPassword: Y
    IBizRemoteSSLAcceptServerCert:
    IBizRemoteConnectionTimeOut: 120
    IBizRemoteForce2002_2003: N
    IBizOEConnection: N
    IBizOETicketGUID:
    IBizOELoginGUID:
    IBizOELoginAsk: Y
    IBizReconnectionDelay: 0
    ColumnNameLen: 50
    UseCaseSensitiveRefNumber: Y
    OptimizerOn: N
    OptimizerDBFolder: C:\Documents and Settings\Owner\Application Data\QODBC Driver for QuickBooks\Optimizer
    OptimizerCurrency: C
    OptimizerDirtyReads: N
    OptimizerUpdateSync: N
    OptimizerEncrytionOn: Y
    ShortCircuitOptimizeFields: Y
    UseIterators: Y
    IteratorChunkSize: 500
    IAppLaunchQBUI: N
    IAppAutomaticLogin: Y
    IAppReadOnly: Y
    IAppAllowPersonalData: Y
    ConvertToLongVARCHAR: FALSE
    MaxLONGVARCHAR: 4096
    Convert To LONGVARCHAR: N
    Max LONGVARCHAR: 4096
    OleInitialize - Returned OK
    Logged In User: Owner
    Is a Service: No
    Registration Name:
    RegSerial:
    QODBC Version: 8.00.00.240
    DLL: C:\WINDOWS\system32\fqqb32.dll
    Driver Name: FQQB32.DLL
    Process Count: 1
    Thread Count: 0
    OpenMode: Follow Company
    Include Raw: No
    Version Type: QuickBooks Enterprise Read Only Desktop Edition
    Access Method: QBXMLRP2.DLL (IAuth2)
    Thread ID: 2540
    SDK Module: QBXMLRP2.DLL (IAuth2)


    it stops there and doesn't go any further.

    I'd rather not have to upgrade AlphaFive unless it's guaranteed to solve the problem, but what is puzzling me is why it stopped working after the client upgraded his POS and hadn't touched quickbooks enterprise, the qodbc, or alpha.

    I'm submitting to this forum, because it seems to be the most appropriate place to discuss qodbc and integration with quickbooks. Please let me know if this should be somewhere else.

    Thanks.
    Janine Freitas

    #2
    Re: QODBC, QBES8, AlphaFive V6 integration

    Janine

    Did the location of the QB company file change after the upgrade of QB?

    Check that the DSN: QuickBooks Data is pointing at the right place.

    I've been trying to contact you after Mark gave me your name, but I'm not being successful. I just replied to your email from the board with my cell number. Call that number please or send me a number that I can call you with.
    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

    Working...
    X