Should I port from Microsoft Access?

Should I port from Microsoft Access?

I have a Microsoft Access database I just started. It would be helpful for my purposes if I could prepare for the eventual porting of it into SQL tables and Dreamweaver in a highly secure environment. Its major functions are: bringing in by link an SQL table or XLS file of customers, sending emails, securing by record ownership, monitoring expiry dates. Everything else in it is just data storage. Can you suggest a strategy? Perhaps I should not write it in Access at all, but just wait for the SQL platform.

    Requires Free Membership to View

    Login

    By submitting your registration information to SearchOracle.com you agree to receive email communications from TechTarget and TechTarget partners. We encourage you to read our Privacy Policy which contains important disclosures about how we collect and use your registration and other information. If you reside outside of the United States, by submitting this registration information you consent to having your personal data transferred to and processed in the United States. Your use of SearchOracle.com is governed by our Terms of Use. You may contact us at webmaster@TechTarget.com.

Personally, I'd wait for the non-Access platform if at all possible. This would save you a lot of work for porting of the database. It has been my experience that porting from Microsoft Access to other database platforms is not a trivial task, and the one doing the work might have to spend considerable time doing the porting. This is especially true with the front end of things. MS Access's forms and reports are not easily portable to another application platform deployment.

This was first published in March 2008

Join the conversationComment

Share
Comments

    Results

    Contribute to the conversation

    All fields are required. Comments will appear at the bottom of the article.
    Back to top