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

MS Access as short-term db backend for web app?

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

    MS Access as short-term db backend for web app?

    I'm pretty familiar with Access, but new to Alpha and web apps. I've been asked to help convert an Access db into a web app on a very aggressive timetable - like, yesterday. Alpha5 certainly seems to be the way to go. The Access tables are working as-is in the current Access desktop application, but they are definately not normalized. My question is, would the following approach work for the short term: Focus my attention on building the web app against the existing Access db, leaving it as-is? Would that even work? And if successful, can Access then function as the db behind a live/production web app until I can work on getting it ported to SQL? Very few users would hit the web app simultaneously. Thoughts? Advice? Looking forward to working with Alpha5!

    #2
    Re: MS Access as short-term db backend for web app?

    I'm not an Access guy but everything you suggest seems workable to me. I am assuming that users would not be manipulating data through the Access back-end once you got the web up and running. If so, not sure if that would be problematic or not.
    Peter
    AlphaBase Solutions, LLC

    [email protected]
    https://www.alphabasesolutions.com


    Comment


      #3
      Re: MS Access as short-term db backend for web app?

      Steve,

      Some time back I came across a routine that purports to convert an ACCESS db to MYSQL db. The filename is msa2mys_3_0_0_117.zip. It may be that I got it from here on the board, but if not, I can send you a link to it. File size is 3,190,060 bytes.

      walt

      Comment


        #4
        Re: MS Access as short-term db backend for web app?

        Thanks for the feedback on this. To the first point - correct assumption - users will not be manipulating the Access back-end once it's up and running. Guess I'll roll up my sleeves and see how smoothly this project starts taking shape. Re: the Access to MySQL converter - Thanks for the tip. I believe I located the tool through a link somewhere on here. I did a trial run and it seems like it will be very helpful down the road. Due to the aggressive deadline I'll see if I can get off the ground with Access for now since I'm comfortable with it. Fair size learning curve for me when I make what seems the inevitable move to a true SQL solution. I'm also assuming I should fix the tables before migrating? They work as-is in the desktop app, but they don't all have primary keys, some of the naming isn't very db friendly (spaces, special characters, etc). We'll see how it goes in the next few days. Thanks again!

        Comment

        Working...
        X