For simplicity I've created 2 accdb files, 1 called testBE and one called testFE.
testBE contains one table test. testFE contains one linked table to testBE-test. Both files are on my local hard drive.
How can I prevent the linked table in the front end from completely locking the BE DB? I've gone to options and set 'Default Open Mode' to 'Shared' and 'Default Record Locking' to 'No Locks' but if I open the linked table it creates a .laccdb file for the BE.
Related
I recently split my database with BE being stored on the network drive. When I open the DB and run Linked Table Manager to refresh linked tables, I get an error message that one of the tables has incorrect or long name. Looking at the table name, it refers to one of the tables that I have deleted long time ago (before db has been split and tables linked) and never used it but for some reason Linked Table Manager still sees it somewhere.
I repeat that this table does not exist anymore in my DB as it has been deleted. Do you know what could be the cause of this?
I have an issue with a table that locks over the network using ms-access. I split the database and have a front end with the user interface and the code and the back end with the linked tables.
When I open the front end and want to add data to the table it is locked for entry (no row with the little *). In VB it gives me the "operation must use an updatable query" error when I want to add the data.
This was used to work perfectly but lately I had issues. If I close the front end and go to open directly the linked table on the network I can edit the table without problem. So I should have the rights to edit the files and they are not read only.
Please advise.
Thank you
I have a MS Access Database which has a Linked Table called "Combined" that is from a text file. I have added a new field to the Txt File but this new field is not showing in the Access Table "Combined". I have right-clicked on the "Combined" table in Access and opened up the Linked Table Manager and refreshed the link and it is still not showing. When I go through the process of Linking the Data Source(.txt file) to a new table "Combined2" it shows the new field. I am not sure what I can do to remedy this. I have tried to just create a new linked file and overwrite the table name "Combined" with the linked file but then it makes it so my queries no longer function that were linked to the "Combined" table. Any help would be appreciated.
Drop linked table in Access and create it again. Just refreshing the link in linked tables manager is not enough in case of text files because it creates import specification, which is specific for file format.
How can I easily set the path for the front end to connect to the backend database. Do I have to use the linked table manager every time ?
I found a tool here but it isn't very reliable. There is no simple config to set the back end path ?
When importing a table from another MS-Access database you can choose between a 'table' and a 'linked source'. If you now choose the 'linked source' and then you select the file of the other MS-Access file (where you select the table you want to link to ) you will get the table in your front-end Access as a normal table with one new property 'linked table'.
Now you can do everything on the selected data in both Access environments. The data will be synchronised as soon as you enter one record (make a change in one line and go to the next line). You do not need to visit the linked table manager any more at all.
I am stuck with some legacy back ends using dBase IV, and would like to be able to copy records from one table to another using an Access front end. The simple answer would be to link to the source and destination tables and run an INSERT query or similar.
However, in my situation, the back end is not a single DBF file, but there are several hundred files that I need to dynamically link to for the copy operation. Currently I have to change and refresh the link definition using the TableDefs property (in VBA) every time I wish to perform the copy operation.
The catch is the front end is shared, meaning that each user has to have a separate copy of the FE so that the linked table definitions are not modified by another user.
I was wondering is there an easy way to do this without using linked tables? I could open DAO connections to the source and destination but cannot find any simple way of copying the records (apart from one at a time). Are there anyways around this?
It is possible to run a query using the linked DBF that inserts into a DBF in another location:
INSERT INTO [dBASE III;DATABASE=z:\docs\].[dbf2.dbf]
SELECT *
FROM dbf1;
Or
INSERT INTO dbf1
SELECT *
FROM [dBASE III;DATABASE=z:\docs\].[dbf2.dbf];