By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
424,949 Members | 889 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 424,949 IT Pros & Developers. It's quick & easy.

Well, you know crashes a lot, and what-not

P: 1
Hello to all,

We have ODBC and direct Native Access 2003 apps on a Two DB's maybe 100 Megbyte total. Maybe 10 people on it during the day.


Obviously, MS access is NOT what to you if you actually want to routinely get at your data.

Not unless your down at Northland(s) coffee shop, with theur 20 line items of inventory and three users; (big sales day for them I gather).

As we limp along until we get PostgreSql installed, is there any way to fix the Access DB without tryingto kick everybody off? the .LDB file is famously useless it would seem to find which computer bloew up the data. ANd when it comes down to it.... doesn't matter the thing from first principles can't work too well, not can it?

Any advice on how to hobble thru until reality kicks in?

Thanks to all. At least it doesn't lose anything; (so far).

regards to all,
Dan K

My ref:
51-20733
http://www.thescripts.com/forum/newthread.php?do=newthread&f=142
Oct 26 '06 #1
Share this Question
Share on Google+
5 Replies


PEB
Expert 100+
P: 1,418
PEB
Hi

I think that this is the worst thing in Access! You need to go away everybody to repair or fix your database or have a bit Access on the ldb that locks the mdb!

In fact there is situations when all users are out and the ldb is still existing with read only properties...

So try to diminue the risk of downing of your Access applications...

And find a form that shows who is in the respective Access database! There is a staff like this that works with errors but works! It reads the ldb file and shows you the info...

Search the net on read ldb in Access

:)
Oct 27 '06 #2

NeoPa
Expert Mod 15k+
P: 31,342
If you open the .Ldb file in a text editor it gives a fairly clear indication of who's in it.
BTW If your .Ldb file is locked and your editor won't open locked files just copy / paste the file and look at the copy.
Oct 27 '06 #3

PEB
Expert 100+
P: 1,418
PEB
My suggestion isn't to open the ldb using an editor... It's well encoded...

There is special ldb reader that can be used from Access for the database and gives informaton about the machine that is logged, is there pb with the respective machine, what is the current state also the user that is logged in!


:)
Oct 27 '06 #4

NeoPa
Expert Mod 15k+
P: 31,342
PEB,

Have a look at one of your LDBs - it's not very complicated at all.
It does use nullchars to terminate strings but otherwise it's all ASCII text.
Oct 27 '06 #5

PEB
Expert 100+
P: 1,418
PEB
Yeah :) But the way to retrieve information from it using VB programming especially Access VB is a bit special. :)
Oct 27 '06 #6

Post your reply

Sign in to post your reply or Sign up for a free account.