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



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

MS SQL problems with Windows 10

  • Filter
  • Time
  • Show
Clear All
new posts

  • MS SQL problems with Windows 10

    I have a client running a networked A5v12 desktop application using web style components.
    This works pretty well on their Windows 7 machines but they recently added some new Windows 10 machines which are experiencing problems with their MS SQL backend database.
    The problems seem mainly to be with saving records.
    They are using A5v12 version 3550_4650 as their subscription ended then.
    I have tried installing a recent version of the MS SQL driver which cleared some of their problems but not all of them.
    Any thoughts or recommended SQL driver version would be welcome!

  • #2
    Re: MS SQL problems with Windows 10

    Not saying you are doing anything wrong, but if you had them on runtime(which is the normal) and they needed an updated version, You could just send them an update version for their runtime. That is assuming you have a later version.
    Had a similar issue when one of my insurance clients changed out a computer to windows 10. Understand they are on dbf, so not a sql issue. Also, ones on sql can sometimes fair better with MySQL. At least, I don't hear these same issues from them.
    Dave Mason
    [email protected]
    Skype is dave.mason46


    • #3
      Re: MS SQL problems with Windows 10

      Hi Dave
      I too prefer MySQL but the client has an MS SQL server that I cannot change.
      I seem to remember that I had a similar problem when they first went to Windows 7 - I managed to get around this by installing MS SQL Express on each workstation as this seemed to install a "decent" version of the MS SQL driver - perhaps I need to try this again.
      Don't you just love Microsoft!
      I did wonder if the problem was caused by my use of UX's and web style grids running from a tabbed UI menu rather than their previous forms and desktop grids - the web components are easier and more powerful to use.
      Also they are experiencing a number of javascript error messages particularly when going in and out of grids.
      Have you had any problems using web components in a desktop application?


      • #4
        Re: MS SQL problems with Windows 10

        I NEVER use web components on desktop. I expected problems would come up. My apps are simple in that respect. I only work on/build DT with dbf files. They always seem to work.
        Ted Giles is working a lot with DT and sql now. He had some great ideas that came out to be good. Using those ideas may lean me a bit more to sql, but never MS anything as can be possible. I do have the latest MySQL server on my server for other purposes. Took about 10 minutes to download and install. I can drop Mariasql in with no differences.
        Dave Mason
        [email protected]
        Skype is dave.mason46


        • #5
          Re: MS SQL problems with Windows 10

          I was afraid that you were going to say that about web components!
          I haven't used desktop forms and grids for several years as my later applications have all been web based with a MySQL backend.
          It looks as though it is time to re-learn them and rewrite the application - don't you just love computers / Microsoft!


          • #6
            Re: MS SQL problems with Windows 10

            They wouldn't call them web components if they were designed for the desktop.
            When all the hype was about web on the desktop. I kind of figured there could be issues down the road, so abstained. Thank God. I try to stay off memo's as well, but when working on client's upgrades, sometimes find an over abundance of use. File naming, field naming and index naming are the other ones to be careful of. imqagine gatting a copy of their app and finding 84 tables with names up to 20 characters truncated to 8.3 and same with fields. Fortunately, they had an unbroken copy on their backup. All had to be renamed which meant a ton of re-writes.
            Dave Mason
            [email protected]
            Skype is dave.mason46


            • #7
              Re: MS SQL problems with Windows 10

              Client installing some Windows 10 machines on their network caused problems with my Alpha application - partly alleviated by installing the supposedly latest MSSql driver - Windows basic installs seem to use a more limited driver!
              Last year I re-did their networked desktop application using Alpha web components and this seemed to "complicate" the Windows 10 problems.
              I have now converted these web components using the "Xbasic Script for Desktop Windows" option on the Web control panel right click menu so that the application now uses a form with a tabbed menu where the buttons run the scripts thus produced - this certainly seems to have got rid of the non-MSSql errors although I am awaiting further testing by my client.
              This has stopped me having to totally rewrite their system - the "conversion" scripts run the web components as XDialog windows.

              If they still experience MSSql problems, I will try installing MSSql Express on one of the Windows 10 workstations to see if this makes a difference - I have found before that doing this even though the workstation doesn't use MSSql Express as such, it does seem to install a better driver.
              I have asked Alpha support for their recommendation for an MSSql driver but have not had a reply - desktop seems to be a thing of the past as far as they are concerned.