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

Alpha 5 - Quickbooks

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

    Alpha 5 - Quickbooks

    I have Quickbooks Preimer 2004 Manufacturing.
    I have Alpha 5 ver 5
    I want to be able to move data both ways.
    I was told that qlinker won't work with Qbks 2004 and that I need ver 6 and qodbc.
    Intuit Develper Network has SDK. Will that work with Alpha 5?

    I'm new to Alpha 5 with no experience on programing. I am learning the Alpha 5 now and was wondering which direction to go in order to move data back with Quickbooks and Alpha 5. The SDK looks like a challenge to learn.

    Thanks for your comments!

    David

    #2
    RE: Alpha 5 - Quickbooks

    I'm using QLinker with QB 2004 Pro but I don't know if it works with the Premier version - it seems like it should.

    QLinker works through the SDK. But this is part of the "problem" for many people. Contrary to what I perceive to be popular belief, accounting is an EXTEMELY complex issue and, as a result, many operations are tightly integrated. It's this integration that gets in people's way.

    I've had people ask me to "just put this data in that table" but you can't do that in double entry accounting. Everything has to go into two tables. For example, Rental Income might be balanced against Rental Sales. One request I've heard a number of times is, "Just put this deposit in the checking account." Unfortunately, as just described, this isn't possible. You must put a matching amount in another account as well. Or multiple accounts if it is a split entry; i.e., deposit $500 and 300 is for rental sales, $190 is for miscellaneous sales and $10 is for sales tax.

    If you only want to pull info out of QB to create reports, that may be quite easy - it all depends on what info you are trying to get.

    If you want to take sales from your A5 app and enter it into QB, that may be possible but it won't be easy. QB will have to be set up with all the appropriate accounts and any entries will have to consider both the credited and debited account. If anything is not correct, nothing will be entered. The amounts in each account must balance, the account names must match exactly, and all the correct fields (some of which you may not care about but QB does) must be entered. This is sometimes the hardest part - figuring out which fields are needed.

    For what it's worth, most of my input to QB so far has been via a Journal Entry because the other built-in methods were not appropriate to what I was doing.

    So far, I have no experience in working with QB via ODBC but you should be very careful and realize that anything that bypasses the SDK opens up a myriad of possibilities for ruining the data.

    Best of Luck,
    Cal Locklin
    www.aimsdc.net

    Comment


      #3
      RE: Alpha 5 - Quickbooks

      Please note that many of these issues are accounting/QB related and not A5/QLinker issues.

      QLinker has it's idiosyncrasies but even when you get past those, interfacing with QB is still not something for the faint of heart. Unless it's something you do on a daily basis, it takes a lot of patience and determination to get it right.

      Comment


        #4
        RE: Alpha 5 - Quickbooks

        Hey thanks Cal.

        I run a manufacturing business.
        I am trying to set up a Work order system in Alpha 5.
        I buy items and assemble them and create new items.
        For the time being, I am creating reports in Qbks, printing as a comma delimited file and importing into Alpha 5.
        I am using QBks because I know how to use it and it has all of my data, but QBks has no good way of giving me a Cost of Manufacture.
        I don't know if I need the Qlinker and SDK.
        Here are some of the things I need out of Qbks:
        Average purchase price of Inventory Items not just a purchase total but price per each.
        Then put those numbers in Alph 5 and then create a Cost of Manufacture.
        Then create a price list; Cost, Distributor, Wholesale, Retail.
        Then import back to Qbks.
        Now with all of that said, I may end of using Alpha 5 for my accounting and not need Qbks, SDK or QLinker. it sounds like for the time spent on learning SDK why not use that on learning more about Alpha 5.
        I tried MS Access but never could get over the hump with it but Alpha 5 seems so much easier and more enjoyable to learn.

        Again thanks,

        David

        Comment


          #5
          RE: Alpha 5 - Quickbooks

          David,

          I don't know if this answer will help or confuse - but this is what we do.

          I have a small accounting practice. We use accounting software for our general ledger and payrolls.

          However, we use A5 extensively to create accounting "front-ends" either for our clients to use or that we use in-house to prepare client data to be included in the accounting process. Our method of including that data, is as Cal's, and that is simply creating a Journal Entry into the General Ledger. The JE's created from A5 aren't a problem in terms of the number of entries. To be able to go directly from the A5 application to the accounting module, just isn't worth the effort or data risk to attempt.

          Interestingly enough, Intuit now owns the accounting package that we use and I've toyed with the "direct" link between quickbooks and our package but have not gotten too far. (Other pressing matters) However, there are some functions of Quick books that I don't care for.

          Our logic is to use our accounting package at what it does best and use A5 when we need a custom solution.

          If I were in your situation, (and that doesn't mean I'm correct) I would determine which functions Quick books perform well, and which functions it doesn't perform well. Then I would try and determine the amount of effort that it would take to create an A5 solution. And then see what it would take to marry the two systems.

          This analysis may yield an all A5 solution, or an all Quickbooks solution, or something in between.


          Bill Schone
          WRS Accounting & Computer Services, Inc

          Comment

          Working...
          X