Info in .ldb index files somtimes garbled

[M Skabialka]

Sometimes when I open the .ldb index files in Notepad I can see a list of
users who have the back end open. Other times it is garbage - little
squares and so on. I find it useful to know who has it open if I have the
occasion to make a change to the BE so I can notify users to close out
temporarily.
Why do I see garbage sometimes?

 

[Stefan Hoffmann]

hi,

Sometimes when I open the .ldb index files in Notepad I can see a list of
users who have the back end open. Other times it is garbage - little
squares and so on. I find it useful to know who has it open if I have the
occasion to make a change to the BE so I can notify users to close out
temporarily.
Why do I see garbage sometimes?

Because it is a binary file. It's pure luck, when you can read something
in it.

If you like to get the connected users:

http://www.fmsinc.com/free/newtips/Check.Users.In.Database.txt

mfG
--> stefan <--

 

[Youness]

some body can help me sort a problem with reading Hotmail messages on
windows Live Mail
I can read what ever I receive from other mailboxes except from hotmail
the Following error message is " Le message n'a pas pu être affiché Windows
Live Mail a rencontré un problème inattendu lors de l'affichage de ce
message. Vérifiez si la mémoire ou l'espace disque de votre ordinateur ne
sont pas insuffisants et recommencez."

 

[M Skabialka]

I tried the code and LOGIN_NAME showed the users all as Admin, not their
network login names, which is what I need so I can tell them to close out of
Access. The COMPUTER_NAME is an inventory number created by the hardware
folks, so undecipherable! Is there a tweak to this code to show the login
ID of the users?

 

[Douglas J. Steele]

Access doesn't record network login names, it records the Access UserId.

If you haven't applied Access User-Level Security (so that your users are
required to log in), all users are Admin to Access.

There's no way around that.

You could try using the code in http://www.mvps.org/access/api/api0062.htm
at "The Access Web" to retrieve the id of the user logged into the machine,
but I suspect you need elevated network privileges to make it work.

 

[M Skabialka]

I use environ("username") to get the login name of users for several
functions, but I need to know which people of the 20 or so who have the
front end are actually using the back end database at a particular moment if
I need to change the BE (which only happens occasionally - I needed to add a
new table today).
So far I am batting zero...
Mich

 

[Douglas J. Steele]

I always cringe when people suggest using an environment variable for this
purpose, given how easy it is to reset an environment variable.

All that's necessary is to open a DOS box, use the SET command to set the
USERNAME variable to whatever you want, then open Access using a command
line in that same DOS box. While the USERNAME isn't actually reset, it is
for the duration of that DOS box, so Access will see whatever the user tells
it to see.

Far safer, in my opinion, is to use the GetUserName API call. See
http://www.mvps.org/access/api/api0008.htm at "The Access Web" for a
complete sample.

 

[M Skabialka]

If only I worked with people who could do such a thing, but there isn't one
of the 20 or so who probably knows what a DOS prompt is, let alone what an
environment variable is or that it can be changed. But I will change my
code as you suggest because we all worry about security issues these days.

 

[aaron.kempf]

SQL Server can give you this information in 2 different ways:

a) Profiler
b) sp_who

Thanks

-Aaron

 

[M Skabialka]

I am working in Access 2003 for both the front end and back end. How do I
use the SQL Server information you have suggested?

SQL Server can give you this information in 2 different ways:

a) Profiler
b) sp_who

Thanks

-Aaron

 

[Douglas J. Steele]

You can't. Aaron has a habit of posting SQL Server-related answers whether
they're relevant or not.

 

[aaron.kempf]

Doug;

I'm not sure I agree. I've been 100% on topic for all of my recent
posts.
There is the right way to do things-- and the wrong way to do things.

You MDB kids do things the wrong way. Move to SQL Server and realize
the benefits of the 21st century.

Why recreate the wheel when the Upsizing Wizard will move you to a
free solution that is more scalable and up to 10 times faster?

Seriously-- why should this kid reinvent the wheel instead of moving
to SQL Server?

-Aaron

 

[M Skabialka]

The cost $3799, and the learning curve?

Doug;

I'm not sure I agree. I've been 100% on topic for all of my recent
posts.
There is the right way to do things-- and the wrong way to do things.

You MDB kids do things the wrong way. Move to SQL Server and realize
the benefits of the 21st century.

Why recreate the wheel when the Upsizing Wizard will move you to a
free solution that is more scalable and up to 10 times faster?

Seriously-- why should this kid reinvent the wheel instead of moving
to SQL Server?

-Aaron

 

[aaron.kempf]

Use MSDE or SQL Express.

MSDE = SQL 7.0
MSDE 2.0 = SQL 2000
MSDE 3.0 = SQL 2005 Express Edition

Yes, I do reccomend that you purchase the $49 developers editon of SQL
Server 2000 and / or 2005. It's just worth it, hands down.

And the learning curve? It's the same language-- SQL.

The upsizing wizard does most of the hard work for you. From there;
you've got designer tools that allow you to edit views and sprocs and
tables-- and it is _JUST_ as easy as it is in MDB.

Have you never used an ADP?

-Aaron

 

[M Skabialka]

A couple of years ago I took a class on SQL Server - it seemed very complex
to install and maintain - probably why SQL Server programmers command such
high salaries. Access back ends pretty much maintain themselves, and are
included in the nightly server backups. I have heard about putting SQL
Server Express on PCs, but what if the current database back end is on the
server - doesn't SQL server then have to be installed there and maintained
also? Can you put even Express on a Windows Server? If not, will it have
to be installed on each user PC? Some of my databases are installed at very
secure sites - there is a list of software programs users can install, and
that's it. I doubt if SQL Server Express is on the list.
The language of SQL queries is fairly similar in Access I'll agree, but the
SQL Server Express user interface software is very differernt.
I did not know what an ADP is until I just looked it up. I think if I had
been using ADP I would not be asking these questions.
So many questions - no answers

Use MSDE or SQL Express.

MSDE = SQL 7.0
MSDE 2.0 = SQL 2000
MSDE 3.0 = SQL 2005 Express Edition

Yes, I do reccomend that you purchase the $49 developers editon of SQL
Server 2000 and / or 2005. It's just worth it, hands down.

And the learning curve? It's the same language-- SQL.

The upsizing wizard does most of the hard work for you. From there;
you've got designer tools that allow you to edit views and sprocs and
tables-- and it is _JUST_ as easy as it is in MDB.

Have you never used an ADP?

-Aaron

 

[aaron.kempf]

yes, it will run on desktops; on servers-- wherever you want to use
it.

I like to think of it as an optional component with MS Office--
because MSDE is included on the MS Office Disk.

If I've ever been given a hard time about installing MSDE; I just
explain it as an optional MS Office component and that's the last I
hear of it.

Of course; if you're going to install it you should download the
latest MSDE (I reccomend MSDE over SQL Express _UNLESS_ you have
Access 2007)
and either way-- gosh the SQL Serrver 2005 Management Studio Express--
I think that you can install that anywhere you want to use it; and
it's perfectly legitmate to use it for managing SQL Server 2000
instances (including MSDE).

This means you don't need to spend $49 on the developers edition after
all

-Aaron
MCITP: Database Administrator

 

[aaron.kempf]

and yes; I mainly run around encouraging _EVERYONE_ to move to SQL
Server; mainly for their own financial benefit

Honestly-- I mean well.. LoL

-Aaron

 

[Tony Toews [MVP]]

Why recreate the wheel when the Upsizing Wizard will move you to a
free solution that is more scalable and up to 10 times faster?

10 times faster? In isolated circumstances sure. But in general
performance using SQL Server won't be that much better and can be
significantly worse in some situations.

Seriously-- why should this kid reinvent the wheel instead of moving
to SQL Server?

A lot of extra work and additional unneeded complexity for most users.

Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm
Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/

 

[aaron.kempf]

Well Tony, I disagree. And since I

1) make more money than you do
2) work with more databases than you
3) have more certifications than you
then why don't you go and sell your wares elsewhere?

So let's go through and test this, ok?

a) A lot of extra work
b) additional unneeded complexity

hmm.. let's dig into your theories.

a) It is not more work-- It's a more efficient language.
GUARANTEED. The tools are better for SQL Server, guaranteed. The
language is easier and more powerful _GUARANTEED_. The educational
resources for SQL Server are superior _GUARANTEED_.

These tools are free (ADP and 'SQL Server Management Studio Express
Edition')-- and it still gives design time tools for update queries,
inserts; etc... So how is it that _BETTER_FREE_TOOLS_ make it harder?
Seems to me like it's harder to defend yourself _ALL_ the time, Tony.
Can Access MDB _COMPETE_ with DTS? How about SSIS? Well can they Tony?
So how is it that your development is 'easier'? The tools that I use
for development are 'Easier' and 'More Powerful'.

b) unneeded complexity? Are you kidding me?
This guy is complaining about LDB files that won't let him edit a
database-- and you're giving mis-information about 'unneeded
complexity'?

How is it that the answer to 'LDB Hell' IS _NOT_ moving to SQL
Server? How is that not the right answer.

What do you think that SQL Server can't use LDB files?
Fine-- I'll make a SQL Server database that uses a LDB file
_RIGHT_NOW_ and it won't take me 1 minute.

Does that make you happier?

How about the 'linked table manager'? This isn't necessary in SQL
Server because all databases can talk to each other-- out of the box--
unless you want to secure it otherwise. Then let's talk about compact
and repair-- well SQL Server MSDE and SQL Server 2005 Express-- they
both do this automatically.

So _HOW_ is it that SQL Server is UNEEDED COMPLEXITY?

Honestly

WHERE DO YOU GET OFF, SPREADING MISINFORMATION?

Do you still fight the facts with HYSTERIA?
Do you still give out _FALSE_ propaganda, Tony?

You had better stop following me around Tony and
attacking everything that I say. I will not allow that.

I am warning you right now, Tony. KEEP YOUR DISTANCE FROM ME; I WILL
NOT PUT UP WITH YOUR MIS-INFORMATION _WARFARE_.

I don't know who you are or what you're doing-- following me around
like this-- but I will not put up with it.

NOT FOR ONE MINUTE.

I just finished working in the marketing department at Microsoft; and
I won't accept you stalking me like this.

Thanks

-Aaron

 

[Tony Toews [MVP]]

You had better stop following me around Tony and
attacking everything that I say. I will not allow that.

I am warning you right now, Tony. KEEP YOUR DISTANCE FROM ME; I WILL
NOT PUT UP WITH YOUR MIS-INFORMATION _WARFARE_.

I don't know who you are or what you're doing-- following me around
like this-- but I will not put up with it.

NOT FOR ONE MINUTE.

I just finished working in the marketing department at Microsoft; and
I won't accept you stalking me like this.

This is a public newsgroup. I am not stalking you. I'm replying to
your misinformation.

Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm
Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/