License for Access can't be located

J

jack_65

When trying to install Office 97 in Win XP Home everything installs ok
except Access and it says no license can be found for it. Have never had the
problem before on any other installs . What is it asking for? All the other
apps work just fine.
Jack
 
J

Jeff Conrad

Fairly common bug caused by a font of all things.

See this Microsoft Knowledge Base Article for the solution:

http://support.microsoft.com/?id=141373

And same information here:

http://www.mvps.org/access/bugs/bugs0013.htm

There is a free download to fix the problem but it only works on Windows 98 I believe.

http://support.microsoft.com/?id=191224

--
Jeff Conrad
Access Junkie - MVP
http://home.bendbroadband.com/conradsystems/accessjunkie.html
http://www.access.qbuilt.com/html/articles.html

in message:
 
C

Chris Mills

It's disappointing to see an "MVP" promoting breaking one of the last bastions
of Access security on his web-site.

Chris

"Jeff Conrad" <[email protected]> wrote in message
 
C

Chris Mills

You lost me there Chris.
It is perfectly apparent. I will repeat it for your benefit.

It's disappointing to see an "MVP" promoting breaking one of the last bastions
of Access security on his web-site.

Are you DUMB or something? (mde's). There is nothing you could post, on your
website, to make me more angry. Do you not have applications to protect? Have
you not even thought about commercial program protection?

MVP. PUH!
 
C

Chris Mills

You must remove some of the content of your website. Otherwise I will mount a
campaign supporting your removal as an MVP (which losely means, "a friend of
Access")
 
C

Chris Mills

It is clear that you have no overall concept of what you have posted/promote
on your website.
Were you planning on shutting down Google as well?
All of that information can be found on Google.
No. It doesn't matter if info can be found elsewhere. ALL Security (including
the German Enigma Machine of WW2) relies on a certain amount of ignorance.
That's what I said, ALL Security.

I don't expect an "MVP" to PROMOTE breaking Access security. I thought
Microsoft themselves might be interested in shutting down a site which
blatantly breaks Access security, though they may not care. I at least expect
them to ASSIST in security. There may be a fine line between assisting
security and breaking it, you have broken it in spades.

Let others (other MVP's, anyone), give their opinions. Otherwise, you don't
seem to have the slightest concept what you have done. Which was apparent from
your first post.

Yes. In the absence of other feedback or strategy, I will hound (one of us)
out of this newsgroup.

(A Very Concerned) Chris
(THAT YOU DO NOT SEEM TO EVEN RECOGNISE THE PROBLEM)
 
F

Fred Boer

Dear Chris:

While I agree that the ability to reverse engineer an MDE is a serious
issue, I think that your reaction is excessive, and your attack on, and
threatened harrassment of, Jeff is just plain wrong.

Ignorance may play a role in security, but you seem to suggest that if
security issues aren't discussed then they might "go away". I would suggest
that the opposite is true: if security issues aren't generally discussed,
then developers would live with a false sense of security, since those bent
on circumventing security will be certain to have discovered these security
issues. Believing that "if we just don't discuss these things then we'll be
more secure" is whistling in the dark.

Developers more than anyone should be aware of all issues relating to
security. Otherwise they will be doing their clients a disservice.

Would you suggest that Access's database password is secure? I'm sure you
wouldn't. Would you tell your client that they should not rely on that
password for security? I should hope you would. Knowing about this security
flaw leads to a more secure Access application. And don't forget that there
are less than scrupulous programmers who might charge a fee to the
unsuspecting to "break" their password. I believe Michael Kaplan posted a
password breaking program to forestall just this kind of thing.

Besides, Access, as far as I have seen, has never been promoted as a
"secure" application; generally, it is suggested in newsgroups and
elsewhere, that if you need security, then that is a valid reason to move to
SQL Server, Oracle, etc..

Jeff isn't *promoting* reverse engineering of MDEs. He is providing a link
to those conscientious developers who understand that they need to be
knowledgeable about Access security and its limitations. Knowledge is power!

You asked for opinions; that's mine. I hope you will take the time to
consider your position, Chris. I suspect that the issue is not as clear cut
as you seem to believe. I hope that you will also drop your wrong-headed
threats to harrass Jeff.

Regards,
Fred Boer
 
C

Chris Mills

Thankyou for responding.

You must surely be aware that SQL Server etc does not a jot for program
security.

Michka, bless his heart, was at the time knocking db password BECAUSE there
WAS a better option, User Level security. That has not necessarily been so for
a long time now. Anyway, mde is the end of the line for Access.

The rest of your logic seems to me, shall we say, "tortured"? I am not
suggesting security shouldn't be discussed, including that mde's can be
broken. But to assist in disseminating how to break them, is irresponsible.

YOUR logic has a natural extension: "If it's possible to break into something,
and you know how, then post it so everyone knows". Ultimately this inevitably
means that ALL security breaks down (not just Access). Because someone,
somewhere, knows how to break anything ever invented (otherwise it would be
"write-only")

Regards
Chris
 
F

Fred Boer

Dear Chris:
You must surely be aware that SQL Server etc does not a jot for program
security.

Well, you have me there. Point taken...
YOUR logic has a natural extension: "If it's possible to break into something,
and you know how, then post it so everyone knows". Ultimately this inevitably
means that ALL security breaks down (not just Access). Because someone,
somewhere, knows how to break anything ever invented (otherwise it would be
"write-only")

Well, perhaps, but my point is more like "If it is common knowledge, freely
obtainable by a quick Google search, then it's better to acknowledge and
cope with it than just hope nobody notices". Particularly when the people
who *want* this information will be sure to find it. It certainly is
reducing the idea to the absurd to imagine I think it appropriate that those
who create a security system should assist in breaking their own security!

Regards,
Fred
 
C

Chris Mills

cope with it
How do you suggest "cope with it"?

cope with it...
cope with it...
Ah I think I get it...might as well distribute a completely unsecured mdb in
the first place and save all the bother...
 
F

Fred Boer

Well, I agreed it was a serious issue, and, no, I don't have a solution. I
suppose that will be up to Microsoft. Anyway, I don't really think I have
much more useful to add to the discussion, so, I think I'll bow out of it.

Regards...
Fred
 
C

Chris Mills

Well then, I'll tell you how to cope with it.

I expect to see the least number of references to hacking, and certainly not
being supported/encouraged by an otherwise respected MVP.

Us developers who distribute Access apps professionally (and Jeff Conrad
appears to be one too), have no other methods (for Access) than the supplied
security methods (db password, UL security, mde).

OF COURSE they can be broken. No smartness there, if Jeff was looking for
points. Professional developers, having little choice, rely on most users
either not having the nous, or the reason, to rip us off. And Jeff goes and
posts that crap to "help them"!

Of course, that's not all that security relies on. My programs have a habit of
falling over every so often (I seem to be good at that). And some customer
rings me up. The first thing I do is check them against my client database,
and BINGO!

Nevertheless, Access security is an important first line of defence, Jeff
Conrad.

Thanks again for replying, Fred.
 
T

tumbler

Go to C:\Program Files\Microsoft Office\Templates\Access click on "AcLicens"
....will repair license :)
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top