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 v 4.5 & Sage ODBC Driver

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

    Alpha 5 v 4.5 & Sage ODBC Driver

    Hi

    I have a customer who is using Alpha 5v4.5 under Windows XP SP1 and also has Sage Line 50 v 9.0 and the user is having a problem using the option within Alpha to attach an SQL table.

    The user selects the Sage ODBC driver and links the tables via the Sage ODBC driver.

    Alpha picks up the Sage tables, Alpha is then able to select the Sage table and then save the table that Alpha wants.

    However when the user goes to open the table, the error message s0002; table not found appears.

    Has anyone tried using Alpha 5 v 4.5 with the Sage ODBC driver?

    Robert Stewart

    #2
    RE: Alpha 5 v 4.5 & Sage ODBC Driver

    Attaching external tables ( a5v4.5 or a5v5 ) using ODBC is at best inconsistent. It works with some ODBC databases and not others. What does seem to work consistently in a5v5 is the ODBC import genie. Be aware, this is importing not attaching.

    Comment


      #3
      RE: Alpha 5 v 4.5 & Sage ODBC Driver

      Robert:

      in tables and sets try to add a new database and see if the imported file is there. If it is add it to your database.


      I hope this helps.

      bob adler

      Comment


        #4
        RE: Alpha 5 v 4.5 & Sage ODBC Driver

        Hi

        Thanks for the replies i will get back to the customer and let them know.

        The customer is going to try the ODBC Import Genie and see if this will work better for them.

        Robert Stewart

        Comment


          #5
          RE: Alpha 5 v 4.5 & Sage ODBC Driver

          Have managed to attach a Sage Version 9.00.0023 Sales Ledger table to both version 4.5 and version 5.
          The steps taken were:
          1. Checked the user had access rights in Sage Line 50.
          2. Created a User ODBC source called Own_Accs with the data path of the C:\Program Files\Sage\Accounts\ACCDATA.
          3. There should be a MSSQLSRV.INI file in the Alpha Five program directory. Opened in Notepad and saved as Own_Accs.ini in the C:\WINDOWS directory
          4. In Alpha choose Attach SQL table and choose the ODBC defined in 2 above - Own_Accs.
          5. Entered password and choose Sales_Ledger.
          6. Saved as Own_Sage_Ledger.dbf. All Sage Sales Ledger accounts shown.

          The essentials appear to there must be an ODBC with the same name as the .ini file in the Windows directory e.g. own_accs and you must use the Alpha MSSQLSRV.INI to create the ini file.

          Hope this helps!

          Bob & Jenny Earnshaw
          BusinessPlus (Letchworth) Ltd
          Accredited Sage Line 50 Resellers

          Comment


            #6
            RE: Alpha 5 v 4.5 & Sage ODBC Driver

            Robert:

            I'm not familiar with Sage Line 50, but I have been using ODBC to link to another Sage product "BusinessWorks Gold" and before that "BusinessWorks" V12.5 for more than 3 years now. I also had some problems in setting up the initial ODBC parameters for the links, but once it was done correctly it has worked consistently and reliably ever since. I frankly do not remember the specific problems and their solutions ( I do remember the need to edit the ODBC file to get dates to work properly) but I think the Earnshaws have pointed you in the right direction. The key seems to be having the right ODBC driver and having .ini files named properly and in the right directories. For example, I have one customer that uses BWG for 5 different companies and therefore needs 5 different .ini files (one for each BWG data file) with the SAME NAME as the corresponding BWG data file, and located in the NT directory of the Server and the Windows directories of the WIN98se workstations. I'm not sure if this has helped you any, but at least you know that once the initial setup is done properly, it will work fine thereafter.

            Comment

            Working...
            X