Topics Search

Table Linking From Frontend to Backend With 3rd Database VBA

Table Linking From Frontend to Backend With 3rd Database VBA
Views: 7
I have a split database with a typical frontend and backend. I want to use VBA code to relink to the backend, but I don't want the code to reside in the frontend. I want a third database to open the frontend and then link to the backend tables.

I have done this type of thing several times before by calling a sub in the frontend and using Transferdatabase to do the linking, but Transferdatabase apparently works only for the current database.

Since I am using a third database to do the linking, I believe that Transferdatabase is not applicable."Is there another way besides Transferdatabase to link the tables via code in a 3rd database?".
Sponsored Links:

More topics

 

2007/2010 Usysribbon

Preview
I am converting (hopefully) from 2003 to 2007.
Have created a QAT ribbon xml.
My system is split into a frontend and backend, with the frontend linking to the backend tables, all users have their own frontend.
Can the Usysribbon table be on the backend or does it need to be with the front end
 

Linking tables from password protected Backend db

Preview
In my Frontend db, I use 'J Street Access Relinker' (link), as suggested in another post, to link to my Backend db.

If I protect my Backend db with a password, from the Security menu in Access, it is no longer possible to link to the Backend db, or at least the Frontend can't open the links.

It there a way for me to set the password via code in my frontend db, so the linking can be done
 

Linking frontend access into SQL database

Preview
I have a access 2010. Database which I split into frontend and backend which works well.

I have decided to move the database into SQL, I used the export wizard and moved the database into SQL which seemed to work, and it I look at the backend which SQL made I seem to see mydata, and if I open SQL it seems to be in that to.

But my problem is, how do I link the access frontend to the SQL backend.
 

2010: Frontend with VBA and backend change breaks VBA form calls (onLoad etc)?

Preview
When I have a frontend with VBA (for table additions etc) and a backend (all tables except Switchboard Items), when I change from my test-backend (USB) to the realtime-backend (Network drive/directory) the tables work, but all VBA calls (events like onLoad etc.) break (I get an error message).

The only way I can fix it atm is by using the Compress and repair database,which restores the links between VBA and the forms etc.

What causes this to happen? Is it a known bug in Access 2010?
 

Access 2010: Frontend with VBA and backend change breaks VBA form calls (onLoad etc)?

Preview
When I have a frontend with VBA (for table additions etc) and a backend (all tables except Switchboard Items), when I change from my test-backend (USB) to the realtime-backend (Network drive/directory) the tables work, but all VBA calls (events like onLoad etc.) break (i get an error message). The only way I can fix it atm is by using the Compress and repair database, which restores the links between VBA and the forms etc.

What causes this to happen? Is it a known bug in Access 2010?
 

Frontend showing data, backend not updating

Preview
I have a very strange problem.

I have a backend-database on a network disk shared by 6 users. All users have a frontend client wich they use to administer the datebase. Everything in the frontend looks ok and they can query the latest data. However if I open up the backend database tables nothing has been updated since the middle of december. If I make a copy of the backend I can open it up and create new posts with ID-numbers that has already been taken by the frontend.

Ofcourse I have doublechecked that the clients are connected to the right backend file (there's only on backend file in the directory). Its all very strange and confusing, anyone with a good idea whats going on
 

Linking my SQL backed to frontend

Preview
I have just converted my access backend database into SQL using the access tool, and it seems to be in SQL server which is good, and on the desktop I have a file which seems to bethe access/SQL file which is call database.VCS and a logo which looks like a yellow tube.

But the problem I have is linking the frontend to the backend, if I us the link tool it want a OBDC and not a VCS.
 

Frontend Compact Backend

Preview
I have a database that is split and is set to make a backup copy of itself when it is started. This database loads multiple spreadsheets into a temporary table in the backend, summarizes the data via queries, and appends the summarized data to permanent tables.

Before the database is closed, I would like the user to be able to compact the backend of the database. Is itpossible to compact the backend of a database from the frontend? Or is this something that just needs to be done manually?
 

Importing backend automatically with VBA

Preview
For a database being used in different offices, I want to provide a config page within the DB App itself so that the user can specify a custom path for the database backend for linking.

I've been messing around with it and am able to link to a backend, if I specify in vba the table names from the back end. I'd rather not do this.

I'm also able to load the backend (importing it, it seems) through VBA. If I check the tables for a connect status, it says it's zero, which is what I get if the tables are not linked.

What I want to do is use VBA to link every table in the backend without having to know the names of the tables.

If I try to do a for loop for each tbl.name after loading the database with :

'Set wrkAcc = CreateWorkspace("", "admin", "", dbUseJet)
'Set dbs = wrkAcc.OpenDatabase("C:\testdatabase_be.accdb")

It doesn't seem to want to work. I suppose I need a way to get each table name before linking all the tables with code such as
 

Got a problem with Moving into SQL

Preview
I have moved the backend of the database in SQL using the access wizard which seemed to work ok.

I have tried to link the frontend of the database onto the backend/SQL which I have followed the guide on MS (I hope is right ),

1st have I done it right by only moving the backend into SQL, 2nd when I have linked the frontend to the backend in SQL, I try to open one of the forms and it does not work, when I try and open the table in the frontend I get a message with says"ODBC - Call Failed" and when it opens it only has 63 recordes and not the 4500 which it should have and every field has #Name?