the problem: i want MySQL to read data from Access database on real-time, which means whenever the data is updated in Access, i can click refresh in mysql to update the table.
Not the other way around, i know that access can link to mysql database on real-time. but that's not what i want.
the reason why i need to have such connection is because, we have another app which can only export data into access on daily basis. so only the access file is refreshed.
I have tried to use ODBC server to export access table to mysql table. but that is not on real-time, if i updated any data in access table, the data will not refreshed in mysql.
Related
I have a business user I am migrating to Snowflake that has many MS Access reporting processes that use MS Access Linked Tables that he is attempting to redirect to Snowflake through an ODBC connection. If his ODBC connection specifies a Database, he can see contents of the linked table. If he tries to link a table in a different Database, MS Access can find the table in list of objects but cannot open it. It is like the process to find the table is using the full data dictionary but when you try to link it, it forms a query that lacks the database qualifier.
We have tried most all qualification of including or omitting entries out of the ODBC connection properties including the database. We can think of two work-arounds but neither are ideal because there is a large user community and the reporting is complex and vast. The two backup options are to create a separate driver for each database or to create views in Snowflake under the same database that can be accessed.
Has anybody else encountered this issue and know a better solution? Is it the version of the ODBC driver for Snowflake (which I assume is the most current because the user followed a canned set of download directions created by our IT department).
So we have a writable database that a lot of our product / data people use. This database has recently been migrated to Managed Instance.
We're working on getting them connected to be able to write/update DB records via Access, a functionality they've had before.
Currently, we're looking at starting them from scratch.
We can't seem to find a way to create a connection that allows for updating or changing records. The connection we're setting up allows them to insert / create new records, but the second that create goes through, even the newly created record can't be edited. We get a standard MSAccess writelock error. This is the case on EVERY table we open. Even ones that are essentially never touched.
Here's how we're connecting:
Network: The machines running msAccess are on our "main office" connection, which is peered with a vnet to the Sql Managed Instanfce. We CAN connect to the sql managed instance via ssms from this place, so it shouldn't be a networking issue (we can also insert records, so same thing)
Permissions: I've made sure that I have full sysadmin permissions via our az-sqlprod01-admin AAD group. I can do this same action in SSMS
Method:
Access > External Data > Linked Table Manager > Add:
Next Screen is Table Import, So that once that's finished we have the full table import list. We import those tables without issue.
Once there, I can bring up any table, try to edit anything, and it gives me the write-lock error at the top of this screen.
My Need: is there a way to connect MSAccess to a SQL Managed Instance without getting write-locks 100% of the time?
I'm currently working on a Attendance & Payroll System. The developing appliction should be able to import the data from Finger Print Scanners.
The client already has 15 finger print machines installed at their premises and it exports to an MS Access database with the following fields
Employee ID
Date
Check-In
Check-Out
The system which we are going to develop will have a seperate MySQL Database.
How can i transfer the data in real-time from MS Access to MySQL?
Whenever a user punches their thumb it autmatically updates the MS Access database.
I want to do,
Data Migration for existing data - This is already accomplished
Transfer all real-time new data to MySQL
How can i accomplish the 2nd task?
I tried using an ODBC connector to mysql. it pulls the table from MySQL to MSAccess. I want to it other way around. ie. Pull the data from existing columns and insert it to mapped table in MySQL.
How can i do this?
You don’t need to transfer the new data.
What you do is use linked tables to MySQL so that all data resides on the MySQL server at all times.
Access is perfect able to use “linked” tables to Oracle, or SQL server or MySQL. When you use linked tables, then access functions as before, but ALL table data is live edited and is on the server – no transfer or sync is required.
I created a split Access 2010 database with a backend for just tables and the frontend with queries and forms. The frontend is linked using an OLE DB connection to ArcGIS, which works fine. When the database connection is connected I am unable to modify my forms but I can update and create queries.
Could this be an issue with having the forms bound to my table query? or is it because I am using a table query for the form? I don't know how to update my table records from the form without it being bound to the table.
This is also a multiple user database and other users maybe linking this to ArcGIS and might also need to make modifications.
Thanks.
From the ArcGIS 10.2 help:
Linked tables in Access are not viewable through an OLE DB connection, although Access queries are available. To use the linked table, create a query in Access that references the linked table and connect to the linked table through the query in the OLE DB connection.
http://resources.arcgis.com/en/help/main/10.2/index.html#//005s00000023000000
Does anyone know how to import .dbf file into MS ACcess 2007?
Do you want to do this programmatically?
MS-Access has option to import the tables OR you could create a Linked Table.
EDIT: Open the MS-Access MDB, goto tables. Right click -> Import -> Choose the appropriate database type (could be dbf in your case).
Well a VBA approach to pragmatically pull this information is to create a connection object connecting to the directory of the tables you want to pull from.
After that open a recordset to query what you need from the tables against that connection. A big benefit of directly connecting and scanning is that your not bulking up tables in your database to push you closer to your next repair/compact.
In order to get this connection however I needed some kind of ODBC connector, something the network admins came and installed behind my back when I switched to a new work PC and it suddenly broke upon connection. If this is something you would be using on other users PCs who won't have access to this (if this is a query you will be performing on a normal basis) it may not function properly for others...