MS Access across network share - Permissions?

[dhotman]

Hello everyone,

As someone who's never really used MS Access I need some help
please

We have a requirement to retrieve data from an MS Access database
running on a Windows 2000 server from a J2EE application server
running on a Linux machine.

From the application server point of view using a JDBC connection

makes most sense and as Access does not support JDBC natively we are
using a JDBC - ODBC bridge from EasySoft.

This all works very well as long as the Acess database is on the same
machine that the JDBC - ODBC bridge is installed on but if the Access
database (.mdb file) is on a network share the connection fails. A
little more detail around the configuration.

Machine1:
- MS Access database

Machine2:
- Mapped drive on to network share from machine1
- Easysoft JDBC - ODBC bridge
- System Data Source connecting to the remote mdb file

Machine3:
- J2EE Application server
- JDBC connection to the Easysoft JDBC bridge on machine2

If the mdb file is on machine2 everything works fine but if its on
machine1 then it fails.

I found a knowledge base article on the Easysoft website (http://
www.easysoft.com/support/kb/kb00813.html) that talks about Microsoft
Access .mdb file on a mapped network drive only being accessed by a
named user.

I don't really know what that means because I've checked that the file
is accessible from all of the machines...

Any assistance would be appreciated.
Thank yo

 

[Douglas J. Steele]

Sorry, but it doesn't sound as though you're actually using Access. Using
Access means you're running msaccess.exe so that you can use forms, reports,
macros and VBA modules against the data. You're not doing that. Retrieving
data from a Jet database (an MDB or MDE file) from an external source isn't
really using Access.

It sounds as though your problem is with Easysoft or your system data
source.

Easysoft appears to have their own newsgroups (they're listed at the bottom
of http://www.easysoft.com/support/index.html). You might try reposting your
question there.

Good luck!

 

[Arvin Meyer [MVP]]

Your ODBC or JDBC bridge needs to be on the machine accessing the database
file. The only possible connection that could work is on Machine 2, but
since your application isn't there, that won't work either.

I would put the database file on a server. I would put your application on a
workstation, or if it is only available through the server, I'd put
everything on the server and use a browser, if that's what's required for
your application, or Terminal Services of it is a rich client application.

 

[Jamie Collins]

Sorry, but it doesn't sound as though you're actually using Access. Using
Access means you're running msaccess.exe so that you can use forms, reports,
macros and VBA modules against the data. You're not doing that. Retrieving
data from a Jet database (an MDB or MDE file) from an external source isn't
really using Access.

Consider that with effect from Access 2007 the native engine has been
rebranded from 'Jet' to 'Access database engine' (ACE).

Further consider that Microsoft often uses the phrase 'Access
database' to mean 'Jet database' so I think it's a bit pointless to
admonish the OP for doing something very similar e.g.

http://support.microsoft.com/kb/230501
How To Compact Microsoft Access Database Through ADO
"To compact an Access database using ADO, MDAC 2.1 or later must be
properly installed on the computer."

If they really meant 'Access' rather than 'Jet' then the chances of
Access begin installed but not MDAC would be so unlikely that it
wouldn't be worth mentioning. And where's the equivalent Jet-not-
Access version of the article, which would surely be of greater demand
than an Access-not-Jet one because most Access users use the Access
interface to do a compact.

Jamie.

--

 

[Jamie Collins]

I think your confusion is due to failing to distinguish between
Access (an application for developing database applications) and Jet
(the default database engine that comes with Access, but is also
part of Windows and usable from other development platfors, via COM,
DAO,ADOor ODBC).

Access is not involved in what you are doing.

It's not that simple. I can download this

2007 Office System Driver: Data Connectivity Components
http://www.microsoft.com/downloads/...36-8C28-4598-9B72-EF94E038C891&displaylang=en

and use the Microsoft.ACE.OLEDB.12.0 provider to create and query a
"Microsoft Office Access 2007 (accdb) file" using the Access database
engine. And you would claim I'm not using Access?!

If you don't consider this to be the correct place to ask about Jet-no-
Access, then where? Why are there no Microsoft.Public.Jet.* groups?

Jamie.

--

 

[Douglas J. Steele]

Consider that with effect from Access 2007 the native engine has been
rebranded from 'Jet' to 'Access database engine' (ACE).

Further consider that Microsoft often uses the phrase 'Access
database' to mean 'Jet database' so I think it's a bit pointless to
admonish the OP for doing something very similar e.g.

http://support.microsoft.com/kb/230501
How To Compact Microsoft Access Database Through ADO
"To compact an Access database using ADO, MDAC 2.1 or later must be
properly installed on the computer."

If they really meant 'Access' rather than 'Jet' then the chances of
Access begin installed but not MDAC would be so unlikely that it
wouldn't be worth mentioning. And where's the equivalent Jet-not-
Access version of the article, which would surely be of greater demand
than an Access-not-Jet one because most Access users use the Access
interface to do a compact.

Be as pedantic as you like, Jamie.

The fact of the matter is that his problem appears not to be with Access
(nor any other Microsoft product), but with Easysoft.

 

[Jamie Collins]

Be as pedantic as you like, Jamie.

Thanks <g> but don't try and tell me that "Retrieving data from a Jet
database... isn't really using Access" isn't being pedantic (takes one
to know one <vbg>).

Jamie.

--