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

Converting MS Access to Alpha and SQL

  • Filter
  • Time
  • Show
Clear All
new posts

  • Converting MS Access to Alpha and SQL

    I hope this is the right place to post this.

    I am in the process of moving a full suite of management software from MS Access to Alpha. In the current Access environment we are running a back end MS Access DB on an internal server. In the new Alpha/SQL environment the data will reside on a ZebraHost SQL Server.

    This is a large project that will probably take about a year to convert completely to Alpha - so we're hoping to do it in stages. Our first task is to provide mobile access via Alpha to our field staff. I have written and deployed our fist app. We need to establish an environment where our office staff and field staff can share data on the SQL server with our office still using the MS Access Front End and our field staff using Alpha. To prepare for this I have started migrating our access backend to the SQL server. I have used the Microsoft SQL Migration Assistant for Access to create the tables on the server and migrate the data. The plan was then to link the new SQL files into the Access front end.

    The big issue we're having is DATE fields. When we export the data from Access to SQL and then link it back the dates are now in TEXT format. If I look into the field on the SQL server is says the format is datetime(2). Any suggestions on how I can fix this?

  • #2
    Re: Converting MS Access to Alpha and SQL

    I don't think Access supports Datetime(2). I think if you modify the table to change them to just datetime, or date - if there is no time portion - it will work better when you try to open it in Access.

    I recommend you setup a test table with all of the different date/time formats to see which one(s) work best for you.


    • #3
      Re: Converting MS Access to Alpha and SQL

      Thanks - I did try and found that datetime works.


      • #4
        Re: Converting MS Access to Alpha and SQL

        Hi Darran,
        What tool are you using to convert your Access data to SQL?
        I have run into this exact issue when using the Microsoft SQL Server Migration Assistant (SSMA) for Access
        All you have to do is change the data conversion mappings to use DateTime not DateTime(2) Unless you are concerned about tracking time down to 2 nano seconds then DateTime will serve most people :)
        I have done quite a few Access to SQL conversions, not all for conversion to Alpha, some just because we needed SQL as a backend.



        • #5
          Re: Converting MS Access to Alpha and SQL


          Thanks for the response. I did figure that out and made the change and it works well now. I do have some junk dates in my database that I am cleaning up, but my testing so far is very promising.

          Again thanks for taking the time to help out.



          • #6
            Re: Converting MS Access to Alpha and SQL

            while there is increased precision with datetime2, some clients doesn't support date, time, or datetime2 and force you to convert to a string literal. Specifically Microsoft mentions "down level" ODBC, OLE DB, JDBC, and SqlClient issues with these data types and has a chart showing how each can map the type.

            If value compatability over precision, use datetime