mcarter said:
This one stumped our IT engineers.
I use Microsoft Access to link to ODBC areas.
You going to have to expand a little bit on what you mean by "ODBC areas".
You do realize that MS access does not allow you to link to an access
database via ODBC?
I have used Access for over 5
years now and this has never happened before.
Your leaving out some significant details here. As I said, MS access does
NOT allow you to link to a backend mdb database via ODBC. It's simply not
allowed, and it's not possible. Try this in the linked table manager, and
you'll see that it's simply not legal to use the ODBC driver for JET with
ms-access.
It is very possible that you might be using a ODBC driver and JET to connect
to a mdb file here. That would mean that you using somthing other then
ms-access to connect to this database. The other possiblity is you are
connecting to a non MS access back end database file (and of course your
term of "ODBC areas" hints that you're not connecting to a ms-access back
end).
Either way, you can see the confusion you're creating here, by loosely using
these terms. so you better clarify what you mean by ODBC areas (by the way
I've never heard that term before). Furthermore, as stated MS access can not
connect to an MS access back and via ODBC.
Our systems engineers think
the problem is in Access and cannot find a problem on our systems. This
problem is only happening for one particular table that we have, not all
tables.
We should clarify if you're actually using ODBC here at all? Further more if
those engineers knew what was going on, they would ask you to clarify this
issue also.
My spider tens tells me that this is a possible issue of permissions, on the
database that you're connecting two, but as I said it's not possible to use
ODBC with ms-access to connect to a ms-access back end!
Without more info it is really much of a guessing game right now is to
actually what you're connecting to and how you doing this.
I usually work remotely thru a web interface called Citrix.
I linked to a ODBC table when I was connected directly to our systems
while
in the office and the data in the table was displayed correctly.
You do all we realize that citrix is simply like GotoMyPc, or VNC, or remote
desktop. This is just a remote desktop ability. If you actualy into the
physical office and physically logon to your account on that physical citrix
box you'll likely experience the same problems. As mentioned, citrix is
simply a remote controll desktop viewing software.
So, you should clarifiy when you say "link", are you talking about a front
ms-access applicaton and linking this to a backend mdb? Or by back end, do
you mean linking to some kind of SQL server type database?
Even more interesting, I also can connect to our systems thru VPN,
instead
of Citrix.
Once again you leaving out some extremely important distinctions here. Are
you using a VPN to connect to Citrix (which is VERY common), or are you
using a VPN to give your access front end access to the back end folder with
the mdb file? This would mean that you're actually placing the front and
part of your access application on your computer, and then linking over the
VPN to your back end that resides on a server (and, which server...the
server running citrix, or where??
And, furthermore if you really are linking over a VPN, this is not
recommended approach it all. the first problem with using a split database
over a VPN is performances about 100 times slower than a typical office
network. and a course in some instances what you might actually have usable
performance, the next problem is is any minor disconnection in that VPN will
cause damage to the mdb back end. (however once again at this point I don't
even know if you're using MS access back and, because MS access can link via
ODBC to a jet back end).
I tried the same thing while connected by VPN. I established a
new link to the table, and the data was incorrect data. When I refreshed
the
link, the table did not change to be the correct data as it did for the
connection thru Citrix.
once again, your failing to make significant distinctions are here on the
technologies that you're using.
I think we should start over here bit, because I don't believe you're
actually using ODBC. If you are then you're front end end cannot be
ms-access. and, conversely logic dictates that if your front end is MS
access, then you're back end can not be a mdb file. (since MS access does
not allow the use of ODBC to connect to an access back end).
And course last but not least, it's very possible that you're not using MS
access here all, and you're talking about some other application development
platform, and you're using the jet database engine which ms-access also
happens to use. MS access is certainly not the jet database engine.
Without clarifying these pieces of information I've asked for, even your
systems engineers will not have a clue as to how are approach this problem,
or have any idea where to start looking for a problem.
so,
front end: what is the front and that you are using to connect to the back
end ? (is it ms-access?)
back end: what is the back end database you connecting to? (as I said if
your front end is MS access, and you're back in is MS access, then you're
not using ODBC)
location of back end: assume you're talking about connecting in linking, I
have to assume that you're talking about a split database application, and
you've not even really mentioned in clarified that set up. furthermore,
where are you placing that backend database, are you placing it on the
citrix server also, or to simply being placed on another server machine in
your office that the citrix boxes connecting to?
use of remote systems:
The fact that you're using citrix here is a moot point, and really for the
most part does not come into this issue at all.
