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

When to migrate from Access to SQL

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

    When to migrate from Access to SQL

    I've read that at some point I may need to migrate my database from a MS Access database to a SQL database.

    Sounds like MS SQL Express will be my choice. So can anyone provide some insight as to when I may need to do this and then I was wondering if someone could point me to a tutorial or a list of steps to do this without taking my WEB app down?

    Thanks in advance for your help.

    #2
    Re: When to migrate from Access to SQL

    If your app does not have a lot of traffic (i.e. the app still performs well), and you are happy performing file-based backups, then stick with Access because of its simplicity.
    Otherwise, consider moving up. There are pros and cons to both. I have used both, and can say that using MS Access as a DB backend has been extremely reliable in an in-house intranet environment. For web-based apps (on a remote server), I would more go with SQL because of data management, backups, etc.
    Last edited by agillbb; 02-10-2014, 10:49 AM.

    Comment


      #3
      Re: When to migrate from Access to SQL

      Dale,

      It doesn't have to be all or nothing. Alpha lets you have multiple connection strings, so you can set up the SQL database and create one of your simple tables there, like customer or contact or one of your lookup tables, and set only the grids that add and edit that table and the dropdowns that use it. That way you can gain experience with the SQL before you jump in with both feet. Once you are comfortable, switch everything or continue to convert a few tables at a time.
      Pat Bremkamp
      MindKicks Consulting

      Comment


        #4
        Re: When to migrate from Access to SQL

        Thanks for the advise. Since it's only on our intranet and gets limited hits I think I'll take the slow approach and start looking at a test database to try sql.

        Comment


          #5
          Re: When to migrate from Access to SQL

          hello
          I know one of the forum member uses access as her backend for her professional site and no complaints.
          when I find her name I will post it.
          you can still use access since you are comfortable with it.

          I am pretty sure it is
          kingcarol
          you can pm her and see if what I am saying is true and if she has had any problems.
          Last edited by GGandhi; 02-10-2014, 11:14 AM.
          thanks for reading

          gandhi

          version 11 3381 - 4096
          mysql backend
          http://www.alphawebprogramming.blogspot.com
          [email protected]
          Skype:[email protected]
          1 914 924 5171

          Comment


            #6
            Re: When to migrate from Access to SQL

            If you do migrate, the easiest way IMHO is to get a test environment with both the access files and an sql instance running on your PC. Then, with the right drivers and the SQL server management studio you can just query your access files and dump them into SQL tables.

            An example of SQL querying an Acess DB file looks something like this:

            Code:
            SELECT *
            from OPENDATASOURCE
            ('Microsoft.Jet.OLEDB.4.0','Data Source=c:\TRANSFER\MP250DB.MDB')...[INVY]
            I've converted numerous Access DB's over to SQL in this way. You can clean the tables and add a Unique ID field (if they don't currently contain one) as part of the query that dumps them in.
            Last edited by -Jinx-; 02-12-2014, 12:51 PM.

            Comment


              #7
              Re: When to migrate from Access to SQL

              Pat,

              This is a very helpful clarification; thanks!

              --Rob Polley

              Comment

              Working...
              X