ODBC

[Guest]

Scenario:
We have an MS Access database that links to ODBC tables in another database
and also has a few access tables. The ODBC links are from a commercial
system and we cannot change them.

We need to share our Access DB (including the ODBC tables) with several
users. Is there a clean & simple way to do this? If not, what is the best
way? We also want to access one of the Access tables via the web using
FrontPage.

We tried creating an ODBC definition to the DB on the server, but it seems
that ODBC on top of ODBC won't work. Can somebody verify this?

TIA
Carl

 

[Jeff Boyce]

Carl

I may not be visualizing your setup, so take this with several grains of
salt...

If you consider the MDB file in which you link to your other data sources as
a "back-end", it seems likely you'd be able to create a "front-end" MDB file
to install on PCs/desktops, and link from there to the back-end "tables".
Or are you saying you've tried this and can't "skip" to the linked-in
tables?

Regards

Jeff Boyce
<Access MVP>

 

[Guest]

OK. There's an MDB on the server that has the ODBC links plus some tables.
I can, from another PC open the MDB file on the server but get an ODBC error
when I try to open one of the linked tables.

So, I cannot access the MDB directly nor can I create a new MDB and use ODBC
to get to the MDB file on the server.

I'm presuming there must be a way to do this. I'm just not sure how
convoluted it would be.

Thanks again.
Carl

 

[Guest]

Let me try to clarify the setup:

Commercial Application with Many FoxPro Files
|
ODBC Defined by and came with the application. Call it AppODBC
|
MS Access DB (call it AppMSAccess) using AppODBC to see the FoxPro files
Also contains a few user created tables
|
PC from user that created the AppMSAccess MDB. He can access all

Now when other users try to access AppMSAccess MDB, they can't. I tried
opening AppMSAccess directly and I tried creating an MS Access ODBC to it.
Neither is working.

The goal is to have several users access AppMSAccess.

Thanks
Carl

 

[Albert D.Kallal]

Well, in the first place, REGARDLESS of that other commercial system, you
REALLY need to use a split database.

The fact of the matter is that the odbc connection stuff needs to be
configured on EACH pc.

So, first, split your database, and if you don't understand why you must do
this, then read the following article of mine:

http://www.members.shaw.ca/AlbertKallal/Articles/split/index.htm

You problem is that the odbc configuration needs to be setup on each pc, and
in fact the software you and your developer team have built with ms-access
also needs to be installed on each pc.