Home/ Questions/Q 6651501
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-26T01:01:13+00:00

I’m planning to create an VB.net application for retrieving data from a database (MS

  • 0

I’m planning to create an VB.net application for retrieving data from a database (MS Access) and store it to a web server (MySQL data base). I really have confusion in my mind. I’m planning to use task scheduler so that the program will automatically run. I’m planning to set the time every 5 minutes.

How can I avoid the redundancy of data?

For example, I’m planning to get the sales for 5 minutes, after 5 minutes I will do it again. I think there will be redundancy in that case. I would like to ask your ideas about this scenario: how would you handle it?

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    In a comment you said “i dont have any idea about how to replace the native tables with ODBC“.

    Is that the only obstacle which prevents you consolidating the data into one set in MySQL? If so, try this suggestion for setting ODBC links to MySQL tables.

    Install an ODBC driver for MySQL, if you don’t have one already. The latest version is available here: Download Connector/ODBC

    Create a DSN (Data Source Name) for your MySQL database from the Windows ODBC Data Source Administrator.

    Create a new Access database and use the DSN to create links with guidance from the web page link @jmoreno provided.

    If the Access names of the linked tables are different than the names you originally used for the native Access tables, change them to match those original names.

    Then you can import your forms, queries, reports, etc. from the old Access application. Ideally everything will just work, since Access will find the table names it needs and won’t care that they are external instead of native tables. However you many need to resolve any data type incompatibilities between Access and MySQL.

    You would need the MySQL ODBC driver on each machine where the Access application is used. Personally I would prefer to deal with that rather than the challenges of synchronizing between separate Access and MySQL data stores. (YMMV)

    When you’re ready to deploy, you can convert the ODBC links to DSN-less connections so the client machines wouldn’t need to each have the DSN configured. See Using DSN-Less Connections by Doug Steele, Access MVP, for detailed instructions.

    • 0