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

ODBC and Sage Accounts

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

  • ODBC and Sage Accounts

    When trying to create a passive link table to connect to Sage Line 50 V9 everything goes great and when I test the connection thats shows that it has succeeded but as soon as I click the "next" button to select the tables to link to Alpha instantly crashes back to the desktop.
    Bob Whitaker
    Bob Whitaker


  • #2
    Re: ODBC and Sage Accounts

    Bob,
    I have done this successfully. What I did was configure a new data source using the mas90 4.0 osbc driver, and in the logon potab of the configuraton dialog, I put in a specific company and a user code with a password.Until I did this ,I was unsuccessful
    John

    Comment


    • #3
      Re: ODBC and Sage Accounts

      of course I meant odbc not osbc and potab is another typo

      Comment


      • #4
        Re: ODBC and Sage Accounts

        Just wondering, does MAS 90 use pervasive sql like Peachtree? I spoke to Peachtree about linking to their data and they said it was a proprietary version of Pervasive and there was no API, no driver, no way to link anything. If it can be linked that would be great.

        Russ

        Comment


        • #5
          Re: ODBC and Sage Accounts

          I was using the 32 bit ODBC driver that comes with Sage, I succesfully connected but it was when I clicked next that Alpha crashed.
          What is the driver John refers to and where did he get it ?

          Bob
          Bob Whitaker

          Comment


          • #6
            Re: ODBC and Sage Accounts

            Bob,
            what version of Mas90 are you using.I was using 4.05, and this driver is most likely added when installing levels 4 and above
            Russ,

            Comment


            • #7
              Re: ODBC and Sage Accounts

              Russ,
              I was under the impression that there was something that one could purchasew that allowed crystal to talk to Peachtree. So they probably sell an odbc driver with a dictionary for their data.
              John

              Comment


              • #8
                Re: ODBC and Sage Accounts

                Russ,I did aearch on crystal and peachtree. It looks like if you have 2005 premium edition and higher, you have a crystal report option. If that is true, there must be an odbc driver forthis level of Peachtree. There may very well be no option for your level of Peachtree other than upgrading.

                Comment


                • #9
                  Re: ODBC and Sage Accounts

                  Yeah, I asked them about that as I already have Crystal, although I'd have to dust it off. The version of Crystal that comes from peachtree is custom for Peachtree so they say that's all that can be used with it. It's not that big a deal as they allow import and export via csv. For what I want to do that should work although a bit clunky.

                  Russ

                  Comment


                  • #10
                    Re: ODBC and Sage Accounts

                    Originally posted by Bob Whitaker View Post
                    I was using the 32 bit ODBC driver that comes with Sage, I succesfully connected but it was when I clicked next that Alpha crashed.
                    What is the driver John refers to and where did he get it ?

                    Bob
                    I have managed to create a Passive-Link connection to Sage Line 50 Version 12 using the Sage ODBC driver.

                    Like you, I succesfully connected but when I clicked "Next" it didn't crash. However, I couldn't see any of the Sage tables so I decided to use the option "Portable" SQL Statement and entered the following:

                    SELECT ACCOUNT_REF, NAME, ADDRESS_1, ADDRESS_2, ADDRESS_3, ADDRESS_4, ADDRESS_5, C_ADDRESS_1, C_ADDRESS_2, C_ADDRESS_3, C_ADDRESS_4, C_ADDRESS_5, CONTACT_NAME, TELEPHONE, TELEPHONE_2, FAX, E_MAIL, WEB_ADDRESS, TRADE_CONTACT, DEL_NAME, DEL_ADDRESS_1, DEL_ADDRESS_2, DEL_ADDRESS_3, DEL_ADDRESS_4, DEL_ADDRESS_5, DEL_CONTACT_NAME, DEL_TELEPHONE, DEL_FAX, ANALYSIS_1, ANALYSIS_2, ANALYSIS_3, DEPT_NUMBER, DEPT_NAME, STATUS_NUMBER, STATUS_TEXT, DEF_TAX_CODE, DEF_NOM_CODE, VAT_REG_NUMBER, CURRENCY, COUNTRY_CODE, DISCOUNT_TYPE, DISCOUNT_RATE, PRICING_REF, SETTLEMENT_DISC_RATE, SETTLEMENT_DUE_DAYS, PAYMENT_DUE_DAYS, CREDIT_LIMIT, ACCOUNT_ON_HOLD, TERMS, RESTRICT_MAIL, TERMS_AGREED, DATE_ACCOUNT_OPENED, DATE_NEXT_CREDIT, DATE_LAST_CREDIT, CREDIT_POSITION, CREDIT_POS_CODE, CAN_CHARGE, BUREAU_CODE, CREDIT_REF, DATE_CREDIT_APPLIED, DATE_CREDIT_RECEIVED, OVERRIDE_TAX_CODE, LAST_PAYMENT_DATE, FIRST_INV_DATE, LAST_INV_DATE, BALANCE, TURNOVER_MTD, TURNOVER_YTD, PRIOR_YEAR, DEFAULT_FUND_ID, GIFT_AID, INVOICE_BF, INVOICE_MTH1, INVOICE_MTH2, INVOICE_MTH3, INVOICE_MTH4, INVOICE_MTH5, INVOICE_MTH6, INVOICE_MTH7, INVOICE_MTH8, INVOICE_MTH9, INVOICE_MTH10, INVOICE_MTH11, INVOICE_MTH12, INVOICE_CF, CREDIT_BF, CREDIT_MTH1, CREDIT_MTH2, CREDIT_MTH3, CREDIT_MTH4, CREDIT_MTH5, CREDIT_MTH6, CREDIT_MTH7, CREDIT_MTH8, CREDIT_MTH9, CREDIT_MTH10, CREDIT_MTH11, CREDIT_MTH12, CREDIT_CF, PAYMENT_BF, PAYMENT_MTH1, PAYMENT_MTH2, PAYMENT_MTH3, PAYMENT_MTH4, PAYMENT_MTH5, PAYMENT_MTH6, PAYMENT_MTH7, PAYMENT_MTH8, PAYMENT_MTH9, PAYMENT_MTH10, PAYMENT_MTH11, PAYMENT_MTH12, PAYMENT_CF FROM SALES_LEDGER

                    I've now got a Passive_link table called Sage_Cust as the Sales Ledger is the Customer table. I managed to create a form and to refresh the data.
                    Jenny Earnshaw
                    BusinessPlus (Letchworth) Ltd

                    Comment


                    • #11
                      Re: ODBC and Sage Accounts

                      Thanks Jenny and all

                      It seems a lot of work to do something that should just work. Hopefully Alpha will look at this and come up with a solution.

                      Regards
                      Bob
                      Bob Whitaker

                      Comment


                      • #12
                        Re: ODBC and Sage Accounts

                        Russ,
                        Russ,
                        My guess is that the only thing custom about it is that it comes with an odbc driver for Peachtree and some ddf files(data dictionary) for peachtree.do you haveversion 2005
                        Peachtree may not be in a hurry to sho their file srtructures to folks ub=nless they make a purchase from them.
                        John

                        Comment


                        • #13
                          Re: ODBC and Sage Accounts

                          Bob,

                          I was looking for an answer to this as well. Crystal Reports opens the tables via SDO without a problem. The SQL suggestion from Jenny could have been:- "select * from sales_ledger". That works ok but these 'passive' links do not auto-refresh (I think). The real problem with Sage is that the actual files are an ancient flat-file design and that design is not sql friendly - you only have to see the new Report Designer to see where they have added horrible functions to provide data in a useable form. I would not do anything serious win this area until they migrate to a real database (not holding breath...).

                          Cheers

                          Comment


                          • #14
                            Re: ODBC and Sage Accounts

                            As i mentioned quite a while ago in this thread, if you are using a version of mas90 4.0 and above mas90 has a new odbcdriver MAS 90 4.0 ODBC Driver and everything works just fine.However if you plan to use it quite a bit you're probably better off creating a special dsn for this use and putting a company, user code and password in the ODBC configuration setup otherwise you will be prompted for these time and time again
                            Ther is no problem with the types of files Sage uses, the ODBC driver takes care of that.
                            It displays all the mas90 tables properly and everything else works as it's supposed to.

                            Comment


                            • #15
                              Re: ODBC and Sage Accounts

                              John,

                              Thanks, I did indeed see your post.

                              Bob was looking specifically for Sage Line 50 - a UK product which has a small entry price (sub $700). The MAS software you refer to is from a long line of companies hoovered up by Sage in its bid for global dominance. I'm certain it's an excellent product but you wouldn't typically buy both - you might upgrade from Line 50 to something like MAS but not in the UK where it does not appear for sale. As to if you could just buy the driver...

                              Regards

                              Martin

                              Comment

                              Working...
                              X