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

MySQL Native versus ODBC issue

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

    MySQL Native versus ODBC issue

    I am reposting this in this forum....

    I am having an issue with data (integrity or display) while accessing a database sitting on a remote MySQL instance residing on a Netware 6.5 sp8 server.

    I am able to access the tables of the database using both the native mysql access and the MySQL ODBC 3.51 client.

    The issue is the native access does not list the records within the table. It show the same information for each record. (although it does recognize the correct number of records in the table, it repeats record number 1 data.)

    Using the ODBC connection, the information is displayed properly.

    Also, when setting up a active-link definition, the native mysql chokes on the logical fields and displays them as type Z, while ODBC properly identifies them as logical.

    Why is this ? I am under the assumption that native mysql would be faster and more "data" safe, but I am seeing otherwise....?
    Attached is the image of the default browse that is displayed after making the connection.

    One active-link connection is native the other odbc. Both are reading the same table from the same database in MySql.

    #2
    Re: MySQL Native versus ODBC issue

    I haven't seen either problem with accessing MySQL, either on a Linux server or a Windows server. I haven't used a Netware server so I can't answer whether there's something peculiar there.
    Can you try the same tables on a locally hosted MySQL instance to see if it's some weirdness about your table that causes Alpha Five to choke?

    Comment


      #3
      Re: MySQL Native versus ODBC issue

      OpenOffice 3.1 has a native mysql connector.

      When I attach to the database and query the table using OO_3.1 native, the data all appears as it should.

      When I use EZQuery and Cherry City Software's OLEDB connector, the data shows up properly.

      MySqlAdministrator displays the data properly.

      All using the same full access user & password to access the data.

      Any ideas on what might be the problem ? It seems, by deduction, that it is not the Netware server, or an access rights issue and since the ODBC within Alpha works, the only other possibilty is the native driver in A5v9.

      BTW, the MySql version is 5.0.81

      Comment


        #4
        Re: MySQL Native versus ODBC issue

        I discovered something interesting.

        My previous issue using the native mysql driver only occurs when I have ALL FIELDS selected to display in the link definition. I changed my native driver to select only 10 fields from the table and now the fields display correctly.

        Anyone else have this issue ?

        Comment


          #5
          Re: MySQL Native versus ODBC issue

          Ok, here is the detail on above

          If I select 79 fields in the active link definition, it properly displays all the fields in the default browse. However, if the definition has 80 or more fields selected, the default browse becomes extremely laggy and displays the information from the first record for all records and fields.

          Why would the ODBC connector work with all fields selected but not the native mySQL connector ?

          Comment

          Working...
          X