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

ODBC Woes

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

    ODBC Woes

    I'm having some problems attaching to an SQL data source in A5v5.

    The data resides in MS SQL Server on a networked fileserver. I have defined the odbc data sources on my workstation. Here's what's happening:

    -Open A5v5
    -File | New
    -Create Vendors.adb
    -rt-clk in tables/sets in control panel
    -select Attach SQL Table
    -select odbc data source | ok
    -enter db password | ok
    -select table (dbo.tblAPVendor) | ok
    -assign filename to attached sql table (vendors.dbf) | ok
    -vendors appears under Tables/Sets
    -rt-clk vendors, select open default browse

    no records appear | close

    -rt-clk vendors, select open default form

    no records appear | close

    try creating new form based on vendors. no records. tried refreshing. nada.

    Oh, and the table structure is there. the field names, types, etc. Just no data.

    Hmmmm...

    Just to confirm that the odbc connection is working fine, I was able to quickly attach to the same data source and create a frontend using Lotus Approach. All records show up and behave fine from there.

    Could this be part of the ODBC bugs I've seen mentioned here on the forum? I was really hoping to us A5 for this project I'm starting, but ODBC connectivity is a MUST (I'm building an auxilliary app to attach to a clients accounting system).

    Any ideas?


    Roy.

    #2
    RE: ODBC Woes

    Alpha 5 & ODBC as a front-end for SQL is pretty much worthless at this point. Supposedly, when the ADO version of Alpha 5 is released this will be corrected.

    Comment


      #3
      RE: ODBC Woes

      Well, that blows... and just when I'm finally ready to make the commitment to switch dev platforms.

      I was really hoping to cut my A5 teeth on this project.

      So, should I conclude that while A5 holds great value for apps where its native data format is used, it is sorely lacking when it comes to live linking to other data sources?

      Guess it's back to Approach. Or heaven forbid, Access. :(

      Comment


        #4
        RE: ODBC Woes

        Roy

        You should try the ODBC Import wizard. It will import data into Alpha 5 tables. If you can work with that model, you'll have better luck until the ADO is available.
        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: ODBC Woes

          The problem is that live access to the data is pretty important.

          I think that for the application I'm targetting, using Imports is way too big of a workaround. (Imagine each workstation having to Import the entire GL before running a report.. and that's just ONE table example... most data entry apps will require opening quite a few tables simultaneously. Throw in several users working on the same tables simultaneously... Then I'd have to deal w/ getting updated tables BACK into SQL Server... not pretty.)

          Short of an ODBC fix, things are looking grim for my first attempt at an A5 project.

          Comment

          Working...
          X