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 problem, Auto ID application

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

    ODBC problem, Auto ID application

    Inherited application when the focus became Wireless Auto ID.

    Using A5V5, 1 License with 10 user runtime, was developed on XP machine. Using a intermdiary program from the scanners on the warehouse floor to the database on XP machine all worked fine. Have two scanner and three actual users. Now that I have bundled this up to move to the server, Windows 2000, the scanning works until the first desktop user accesses the database, then the scanners pop up with ODBC errors, the intermdiary program error is database in use by another user, or need username and password. Is there something I have missed in the setup with runtime. I did download a trial of full version to the server, this did not help, will it help if I purchase an additional full user license?

    Again, this application was completely functional with 3 desktop users and 2 scanners through intermediary software until the move to the server.

    Thanks in Advance
    Zina

    #2
    RE: ODBC problem, Auto ID application

    Hi Zina,

    It is hard to answer due to not knowing about the intermdiary program.

    Fist thought is why use the intermdiar program for scanning - if that is what it is being used for? You can scan directly into the A5 database. It almost sounds like the intermdiary program is not commiting the record, causing the problem.

    On the set up of A5, are the desktops network optimized? In otherwords is a shadow verison of A5 installed on each desktop.

    You do not need to put a full version of Alpha 5 on the server. On the server all you need is the application and data files. The runtime should be installed on the desktops, then network optimized (a built in funtion of A5) to the server.

    Hope this helps.

    Dan
    Dan

    Dan Blank builds Databases
    Skype: danblank

    Comment


      #3
      RE: ODBC problem, Auto ID application

      The program interfacing with the scanners is called NetS24 by Symbol, the scanners themselves are running MCL Collection and is necessary for the application running on the scanners. And it has worked completely with this database application until the move was made to the server. It commits the information up until the one of the desktop users connects to the database, then it rejects the scanner data. I can view the data attempting to be written in the log, it is rejected by Alpha.

      Thanks for your response.

      Comment


        #4
        RE: ODBC problem, Auto ID application

        From what you describe it sounds like a table might be open in Alpha. When the desktop user connects is a record being written? Is there a log on process that is not being completed?

        Just some thoughts.

        Dan
        Dan

        Dan Blank builds Databases
        Skype: danblank

        Comment


          #5
          RE: ODBC problem, Auto ID application

          Thanks for your thoughts, I ended up working around for now, which has actually sped up the scanning process, until I can figure out what the two differences are. I will look at the open table issue, very possible that when the program was bundled up through runtime, something was open. I don't know how that would happen, but imagine something along that line is possible.

          Thank you Dan!
          Zina

          Comment


            #6
            RE: ODBC problem, Auto ID application

            Be careful when you move things to a Server.
            All users(machines) need to be known to the server with full rights and permissions to access databases and tables on the server.

            My gut feeling is that there is nothing wrong with your application, but that there may be some sort of permission issue with the server.

            Does the intermediary application have permission to access the server? Does it have full rights to the a5 folders?

            Comment


              #7
              RE: ODBC problem, Auto ID application

              Thanks for your input, I have worked around the issue, but still am perplexed. When no other user has attached to the database, the application worked perfectly. The information being scanned in the warehouse hit the log and then to the database. As soon as a desktop user opened the database, or specifically a table being written to, then the scanners crashed, the intermediary software has the capacity to send a user name and password, but if that was necessary, why would it work if it was the solely accessing the data table. I added a table specifically for the receiving of the data, and it works great, and a quick manual update moves the data to the working table. But, it has taken away the 100% real time that we enjoyed on the XP machine. This is my first time using Alpha for this specific purpose, I am more on the auto id side. The client is still pleased with the application, but I am still hoping to figure this out, for the next time around.

              Thanks again I will take a look at the password/username possibility.

              Comment

              Working...
              X