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

Painful DbfTransition to SQL SERVER or MYSQL

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

    Painful DbfTransition to SQL SERVER or MYSQL

    It is very frustrating to use dbf on a network environment, after making a lot of novice questions on the desktop thread, and with the help of alpha five experts who are very willing to help, I was able to produce a simple application. At first it is also frustrating to see unneeded results, and with reindexing fixes it all.The application is running smoothly on a single pc, However when I installed the app in another pc to access the shared alpha database, I found out that it is taking too much time to load queries and filters with about much records on a single table, I tried the data in a Microsoft access and sad to say that microsoft access is faster in producing query results. That's why I then decided to start all over again using SQL server or MYSQL, the first thing that I would do is to load a million records and try to access it on a network using the Grid component of alpha five, The main advantage of using the native dbf of alpha is that, coding of add,edit delete, and find is minimized or no code at all. Is it possible to transfer all the dbf tables to MYSQL or SQL Server 2008 express edition?

    #2
    Re: Painful DbfTransition to SQL SERVER or MYSQL

    Originally posted by JetLi View Post
    It is very frustrating to use dbf on a network environment, after making a lot of novice questions on the desktop thread, and with the help of alpha five experts who are very willing to help, I was able to produce a simple application. At first it is also frustrating to see unneeded results, and with reindexing fixes it all.The application is running smoothly on a single pc, However when I installed the app in another pc to access the shared alpha database, I found out that it is taking too much time to load queries and filters with about much records on a single table, I tried the data in a Microsoft access and sad to say that microsoft access is faster in producing query results. That's why I then decided to start all over again using SQL server or MYSQL, the first thing that I would do is to load a million records and try to access it on a network using the Grid component of alpha five, The main advantage of using the native dbf of alpha is that, coding of add,edit delete, and find is minimized or no code at all. Is it possible to transfer all the dbf tables to MYSQL or SQL Server 2008 express edition?

    in the controlpanel use export data select alphaDao or under Tools the Database Fileupsize genie, good luck!

    Comment


      #3
      Re: Painful DbfTransition to SQL SERVER or MYSQL

      Jetson - if you're managing this many records and are this involved in Alpha, I presume you're a subscriber? One of the videos available (subscriber or not really) is "Xbasic for Web Applications". That and the basic A5v11 web-side tutorials (and so much other advice) have emphasized the advise to create your web apps with a SQL back-end. The Xbasic for Web Applications will give you a really good start to working with MySQL especially, and SQL in general.
      -Steve
      sigpic

      Comment


        #4
        Re: Painful DbfTransition to SQL SERVER or MYSQL

        Originally posted by Steve Workings View Post
        Jetson - if you're managing this many records and are this involved in Alpha, I presume you're a subscriber? One of the videos available (subscriber or not really) is "Xbasic for Web Applications". That and the basic A5v11 web-side tutorials (and so much other advice) have emphasized the advise to create your web apps with a SQL back-end. The Xbasic for Web Applications will give you a really good start to working with MySQL especially, and SQL in general.
        Thank you Steve, I posted something on the Desktop Thread, Titles "Query Speed Tips" but nobody is replying. In your experience as a veteran in alpha, have you encountered a slow querying/filtering in workstations? Is alpha ideal only for a single pc using the native dbf's? I tested JUST a single table making sure that there are not sets involved JUST one table, and I shadowed it on a workstation and tried a query / flter but it is still the same, it is taking over 1 minute to display the result? end users won't like it for sure. What have you been explaining to your customers about the speed?Some say they have 100 workstations? Come on,1 workstation is slow, how much more with 100? maybe this guys are just helping alpha company to market their product, exagerating that they are successfully using 100 workstations 24/7. Please correct me if I'm wrong, just an opinion, and please guide me on how to speed up a query in a workstation with just 240,000 records, I don't know if it will be over a million records. Believe me, Microsoft access displays a query or filter in just seven seconds in a workstation. I disregarded access just because of its database limit which is 2 GB.Thank you.

        Comment


          #5
          Re: Painful DbfTransition to SQL SERVER or MYSQL

          I disregarded access just because of its database limit which is 2 GB.
          I see you're moving the SQL Server direction, and just in view of this quote, be aware that SQL Server Express not only doesn't have a lot of tools that the pay-for versions do, but there are also size limitations. We recently moved from MS SQL to MySQL with that as one reason. Make sure you don't set yourself up to need to migrate again a couple of years from now.

          Comment


            #6
            Re: Painful DbfTransition to SQL SERVER or MYSQL

            I wonder who will charge us more in the end. Oracle or Microsoft?

            Comment


              #7
              Re: Painful DbfTransition to SQL SERVER or MYSQL

              SQL Server Express 2012 allows up to 10 Gb storage - more than some earlier versions of Express. I'm using that for what may turn out to be a huge, huge project with lots of document storage as well, but figure if we start nearing the size limit we'll be well able to afford the move and happy we've come that far. I've already reviewed the upgrade path and it looks straightforward.
              -Steve
              sigpic

              Comment


                #8
                Re: Painful DbfTransition to SQL SERVER or MYSQL

                The thing about the open-source route, though, is that if Oracle started charging more than MS today, there are already several other open source branches from the development of MySQL that could be switched to with little to no effort. We have also found lots more open-source DB tools and other DB-connected applications that are more MySQL friendly than SQL Server; the only negative to these is they're often more Linux-friendly and with Alpha we're fairly well stuck with Windows...

                And Steve, I wish you well and hope your project is successful enough to pay for a larger DB, but why would you want to?

                Comment

                Working...
                X