Linked Table major issues!!!

[Todd C]

Ok, so here is the issue. I have a FE and BE, both were set up on a LAN. The
LAN has been reconfigured with different directories which make the
communication for the FE and BE impossible. Normally, I would just go in the
FE and change it with the Linked Table Manager, however, I set up the FE to
where the everything is locked out unless you have a username/password. The
bypass key is disabled unless an already logged in person enables it.

The first thing the FE does when its loaded is to pull up the login form, in
the background, it also loads a version form that checks the version on a
table. Since it cannot access that table, it boots me right back out. I
cannot mess with the LAN properies due to the LAN drive letters being
changed. How can I solve this problem. Any answers that I havent already
thought of would be greatly appreciated.

 

[Dirk Goldgar]

Ok, so here is the issue. I have a FE and BE, both were set up on a LAN.
The
LAN has been reconfigured with different directories which make the
communication for the FE and BE impossible. Normally, I would just go in
the
FE and change it with the Linked Table Manager, however, I set up the FE
to
where the everything is locked out unless you have a username/password.
The
bypass key is disabled unless an already logged in person enables it.

The first thing the FE does when its loaded is to pull up the login form,
in
the background, it also loads a version form that checks the version on a
table. Since it cannot access that table, it boots me right back out. I
cannot mess with the LAN properies due to the LAN drive letters being
changed. How can I solve this problem. Any answers that I havent already
thought of would be greatly appreciated.

Are you using mapped drive letters? If so, you ought to be able to remap
them temporarily. The old DOS "subst" command, maybe?

How thoroughly (and securely) is the Shift bypass disabled? You may be able
to programmatically change the AllowBypassKey property.

If you can open the database via DAO, you may be able to change the Connect
property in one or more TableDef objects, so as to get at least past the
startup procedures.

 

[a a r o n . k e m p f]

linked tables are obsolete

move to Access Data Projects and you don't need to worry about any of
this junk

 

[Tony Toews [MVP]]

Please ignore Aaron Kempf's posting as Aaron's answer to just about every question is
SQL Server and ADPs. No matter how appropriate his response.

Tony
--
Tony Toews, Microsoft Access MVP
Tony's Main MS Access pages - http://www.granite.ab.ca/accsmstr.htm
Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/
For a convenient utility to keep your users FEs and other files
updated see http://www.autofeupdater.com/
Granite Fleet Manager http://www.granitefleet.com/

 

[a a r o n . k e m p f]

Please ignore Tony Toew's posting as Tony's answer to just about every
question is
Jet- a database that has been obsolete and depecrated since Office
2000 was released.
No matter how appropriate his response.

 

[Larry Linson]

message
Please ignore Tony Toew's posting as Tony's answer to just about every
question is
Jet- a database that has been obsolete and depecrated since Office
2000 was released.
No matter how appropriate his response.

In actual fact, Mr. Kempf, Tony Toews is a strong supporter of using SQL
Server as a back end / data respository when that is an appropriate
solution; in addition, he gives real answers to real problems, not just
recommendations to change the data repository, which is rarely a solution to
an immediate problem.

Secondly, Jet is neither obsolete nor deprecated (not "depecrated" *) ... it
was taken over by the Access team, and has been updated in both Access 2007
and Access 2010, as well as spawning a new engine called ACE which has
additonal data types.

* I assume that would translate to "prepared for shipping by
packing in a depe crate, sealing the depe crate, and calling
a public carrier for pickup".

The newest buzz in the world of Access does not have to do with a server
back end, at all, but a different kind of Web App created in Access using
SharePoint as a data repository. Those are certainly not appropriate for
_every_ situation, and neither is Jet, nor ACE, nor some version of SQL
Server, nor any other ODBC-compliant server database -- but each is
appropriate in _some_situations.

Larry Linson
Microsoft Office Access MVP

 

[a a r o n . k e m p f]

Larry;

He is not a strong support of anything except an obsolete database
engine.

Just because dumb old dipshits are too stupid to use the worlds most
popular database (SQL Server) that doesn't mean that his inability to
learn a real database has any bearing on anything.

Web-enabled Access databases cost what $60,000?

-Aaron

 

[a a r o n . k e m p f]

Access Data Projects are appropriate everywhere-- for example where
you have wireless

most pcs sold today have wireless, and wireless doesnt' work with Jet.

So so so so so so very sorry that Tony tried to move to SQL Server
_ONCE_ and he failed.. and because of that you're stuck in the 80s