Is there a "back door" into an mdb file?

[Guest]

I am troubleshooting an Access database application – one that I didn’t
create - written in either Access 97 or 2000, and has been running in Access
2003, SP3. It resides on a server, and is shared for multiple user access.
It is launched from a PC desktop user shortcut, with the target being a
*.mdw server file. There must be some sort of security module within the
application that tracks user logins, and accumulates total logins.
Yesterday, the when the user launched the shortcut, an error message
displayed, that the user has exceeded user/system login limits. Clicking on
“ok†or closing out the message closes out the database application, and
Access - everything. Guessing an incorrect user login displays an invalid
login message and prompts you to try again. Launching the *.mdb file
without going through the *.mdw file displays a 3112 error.

I think the security module and associated table(s) could be modified, if I
could only get to them. I can’t get to them through the “front†door. Is
there a “back†door, or another way to get into the *.mdb objects without
launching the database application?

Thanks in advance,
Trouble Shooter

 

[Albert D.Kallal]

It resides on a server, and is shared for multiple user access.

It is launched from a PC desktop user shortcut, with the target being a
*.mdw server file.

The above don't sound right. First, while some people mistanlty share a
applation on a server, it is NOT the correct appraoch. this will usealy
result in instiablry, and damaged fiels. In addtion to this being a bad
practive, the "target" launching the mdw file sounds incorrect. So, the
first part of the above tells me that the appclation was setup wrong. The
2nd part about the mdw tells me that either the first infomraton is
incorret, or you simply did not read the shortcut correclity. It is stnadard
fiar to use a shirtodict to speiclfy the mdw file, but NOT without ALSO
speicfing the mdb file.

So, using a shortcut to speiclfy the mdw file is correct, but that shortcut
also needs to speicfy the mdb (or mde) fil to use?
(it is possbile that only a mdw file is speicled, and THEN the user has to
go and browse, and open the mdb file...but this is not likey).

So, what mdb, or mde file is spieced in the shofrt cut ?? (as mentiond, BOTH
the mdb/mde, and mdw file will be specifed in this short cut). Also, by
determings if a mde is used, then we know the appcatio is now NOT in a97
format. If it is a mdb..then it possbile it is still in a97 format...but not
likey.

There must be some sort of security module within the
application that tracks user logins, and accumulates total logins.

Well, as a general codeing practice, many of my appcltions will log the use
"name", and in ms-acces this is found by the currentuser() function.

However, there is noting speical in ms-access that logs this informaton. So,
the develoerps might have writteen some code...but it is not a "sepical"
module or any such thing.

Yesterday, the when the user launched the shortcut, an error message
displayed, that the user has exceeded user/system login limits.

Ok...do remmeber that windows XP only allows 10 users to connect to a box.
After that number, you need to purchase a "server" edtion of windows. This
10 user limit is not one of ms-access, but that of windows XP, and windows
XP home version. (they both are limited to 10 connectons in a file share
sittaion).

Is
there a "back" door, or another way to get into the *.mdb objects
without
launching the database application?

Useally holding down the shift key during startup will bypass the startup
options. If the shift key was disabled, then you might want to contact the
orignal developer.

You can also simply import the objects into another file...but this assumes
you have a logon with permissions to do so (ie: make sure you "join" the
security workgroup..and then create a new mdb...and then import from the
existing one).

And, when you have a minute, check out the reasons for running a split
database, as you REALLY need to do this to ensure reliable operation. You
can read about this here:

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

Also, since you stated that the target is a mdw file..that don't seem
right..but it also hints that the application might very well be split
already. I explain the use of a shortcut, and the use of a security
workgroup file in the above article.

 

[Guest]

I don't think the information you provided correctly reflects the set-up.
The 1st error in you posted may not be an Access error message. In fact it
is likely to be the W2003 Server message since this sounds like a Windows
Client Access License issue. You network may have used all the C.A.L. at the
time.

MDW is a Security file but you don't use it on its own. Suggest you check
the command line in the shortcut on the desktop which should normally have:

* Path to MSAccess.exe
* Path to the database file (MDB or MDE)
* Possibly /user flag and /pwd flag
* /wrkgrp and path to the MDW file.

Check Access Help topic "Statup command-line options" for the full syntax of
a command line (normally used in shortcut icon) to open an Access database.

If the database is secure correctly, you can't open it without specifying
the correct MDW file, the user name and password.

If this is a multi-user application, you really must split the database into
Front-End and Back-End to reduce the chance of corruptions and to facilitate
update / maintenance of the database.

 

[Albert D.Kallal]

geesh...lets try this again with the spell checker....

It resides on a server, and is shared for multiple user access.
It is launched from a PC desktop user shortcut, with the target being a
*.mdw server file.

The above don't sound right. First, while some people mistakenly share a
applation on a server, it is NOT the correct approach. this will usually
result in instability, and damaged files. In addition to this being a bad
proactive, the "target" launching the mdw file sounds incorrect. So, the
first part of the above tells me that the application was setup wrong. The
2nd part about the mdw tells me that either the first information is
incorrect, or you simply did not read the shortcut correctly. It is standard
fair to use a shortcut to specify the mdw file, but NOT without ALSO
specifying the mdb file.

So, using a shortcut to specify the mdw file is correct, but that shortcut
also needs to specify the mdb (or med) fil to use?
(it is possible that only a mdw file is specified, and THEN the user has to
go and browse, and open the mdb file...but this is not likely).

So, what mdb, or mde file is specified in the short cut ?? (as mentioned,
BOTH
the mdb/mde, and mdw file will be specified in this short cut). Also, by
determining if a mde is used, then we know the application is now NOT in a97
format. If it is a mdb..then it possible it is still in a97 format...but not
likely.

There must be some sort of security module within the
application that tracks user logins, and accumulates total logins.

Well, as a general coding practice, many of my applications will log the use
"name", and in ms-access this is found by the currentuser() function.

However, there is noting special in ms-access that logs this information.
So,
the developers might have written some code...but it is not a "special"
module or any such thing.

Yesterday, the when the user launched the shortcut, an error message
displayed, that the user has exceeded user/system login limits.

Ok...do remember that windows XP only allows 10 users to connect to a box.
After that number, you need to purchase a "server" edition of windows. This
10 user limit is not one of ms-access, but that of windows XP, and windows
XP home version. (they both are limited to 10 connections in a file share
situation).

Is
there a "back" door, or another way to get into the *.mdb objects
without
launching the database application?

Usually holding down the shift key during startup will bypass the startup
options. If the shift key was disabled, then you might want to contact the
original developer.

You can also simply import the objects into another file...but this assumes
you have a logon with permissions to do so (ie: make sure you "join" the
security workgroup..and then create a new mdb...and then import from the
existing one).

And, when you have a minute, check out the reasons for running a split
database, as you REALLY need to do this to ensure reliable operation. You
can read about this here:

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

Also, since you stated that the target is a mdw file..that don't seem
right..but it also hints that the application might very well be split
already. I explain the use of a shortcut, and the use of a security
workgroup file in the above article.

 

[Guest]

Okay, the shortcut target has the following format -

"C:\prgeam files\ ... \msaccess.exe" \\srvrname\dirname\database.mdb/wrkgrp
\\srvrname\dirname\filename.mdw

"start in" points to the directory on the server, and the server is running
Windows 2K Pro.

I'll try holding down the shift key while launching and see what that does.

Thanks for using spell checker ...

Trouble Shooter

 

[Guest]

Holding down the shift key while launching took me into the Database view,
where I could get to the db objects. Thanks.

Now the user can use the app, and I can figure out a better way of doing the
login tracking.

Trouble Shooter