469,275 Members | 1,459 Online
Bytes | Developer Community
New Post

Home Posts Topics Members FAQ

Post your question to a community of 469,275 developers. It's quick & easy.

Strange ODBC Behaviour ???


I created an MS Access 2000 front end a long time ago. We use it every
day and everything works great. This MS Access DB is held in a folder
on our Cobalt Qube server. On this server we also have MySQL

I have allready hapilly exported some of the MS Access tables into
MySQL and import-linked back. Again everything works great.

We are working on a small office network using Windows XP.
On my PC I have an odbc connection set up which I used to
import/export tables ,which when tested connects to the MySQL DB and
then lets me into our MS Access front-end on my pc. (this is done by
clicking a shortcut icon on my desktop linked to the MS Access DB on
the server.
On my colleagues PC however, if I open his ODBC admin panel, I have
created the same named ODBC connection as on my PC and when tested
again connects to the MySQL server.

The Problem:

If I try to run the MS Access front end on his machine again via a
shortcut or even going into the folder on the server it denies me
access using odbc ?

How can this be ?
Outside of Access his ODBC conection works perfectly, but when trying
to run Access it says Access denied using the same odbc, using pasword
'yes' ???
Please help, as otherwise this front-end can only be used on my pc ?
Thanks in advance
Nov 12 '05 #1
2 1500
You *REALLY* need to have each user have a copy of the front end (preferable
a mde file). All other software you have from Word, Excel, Outlook etc is
ALWAYS installed on each pc, and you should do the same with software you
develop. The fact that you are all of sudden developing software does not
change the fact that you install the software on each pc.

The above may not solve your problem, but it is a good start. I would
test/try moving the font end to that users pc, and then re-creating the link
to MySql. There may be some issues of passwords, or permissions being saved
with the linked tables.

Regardless if the above fixes your problem, you need to give each user a
their own copy of the application that runs on EACH pc. Virtually all other
software you have is run this way, and there is not reason to run ms-access
this way. It is standard practice, and there is not developer that will tell
you otherwise.

Albert D. Kallal (MVP)
Edmonton, Alberta Canada
Nov 12 '05 #2


Thanks for your response, however I think you missunderstood. We both
have MS Office installed which includes MS Access.

I created a DB with Access and stored it in a folder on our server for
security. I then created a shortcut to it from my desktop and the same
on my colleagues PC. We can both run Access on our PCs. I also created
an ODBC Connection on each PC so that when the DB is run on either PC it
would check the local ODBC connection on that PC to connect to the MySQL

My PC works fine. The ODBC on the other PC connects fine, but when the
Access DB is run on his PC from the shortcut it denies access using that
ODBC connection that I have already tested and got connected....how is
this possible ?
*** Sent via Developersdex http://www.developersdex.com ***
Don't just participate in USENET...get rewarded for it!
Nov 12 '05 #3

This discussion thread is closed

Replies have been disabled for this discussion.

Similar topics

reply views Thread by Nedelcho Stanev | last post: by
2 posts views Thread by Neil | last post: by
3 posts views Thread by Andrew McGregor | last post: by
8 posts views Thread by Dox33 | last post: by
1 post views Thread by CARIGAR | last post: by
reply views Thread by zhoujie | last post: by
By using this site, you agree to our Privacy Policy and Terms of Use.