Re: Acces VBA Password
From: '69 Camaro (ForwardZERO_SPAM.To.69Camaro_at_Spameater.orgZERO_SPAM)
Date: 11/30/04
- Next message: '69 Camaro: "Re: DB Compact causes loss of Windows file permissions"
- Previous message: Jean: "DB Compact causes loss of Windows file permissions"
- In reply to: altan: "Re: Acces VBA Password"
- Next in thread: altan: "Re: Acces VBA Password"
- Reply: altan: "Re: Acces VBA Password"
- Messages sorted by: [ date ] [ thread ]
Date: Tue, 30 Nov 2004 14:13:15 -0800
Hi.
> I am not a true novice in designing databases,
You've given this perception. It's rather like the adage, "Possession is
nine-tenths of the law." Well, perception is nine-tenths of reality.
People perceive an idea and then act on that idea. You'll find that it
doesn't much matter whether or not that idea is a fact.
For example, when you first meet a person, you have about three seconds to
make a good impression. If you use that window of opportunity to make a bad
impression, it takes a tremendous amount of effort to overcome that person's
first impression of you -- if you _can_ overcome that bad first impression.
You'll be living with the reality made from that first impression, so it's
usually worth the effort to make a good impression.
Have you noticed that if people perceive you as a genius on first
impression, then they'll treat you as they treat other geniuses that they
have met? On the other hand, if people perceive you as "a few sandwiches
shy of a picnic basket," then they'll treat you as if "the elevator doesn't
go all the way to the top."
> When I want to create the MDE file before packaging
> the product, the Make MDE file selection is not enabled on the Tools,
> Database Utilies menu. On going through to the help on this matter, it
tells
> me
There can be a number of reasons that the "Make MDE File..." menu option is
not available. Check the "Can't make an MDE!" checklist at the following
Web page to help you determine why you can't create the MDE database:
http://www.Access.QBuilt.com/html/conversion.html
> 1. You must have password access to the Visual Basic code. "
This sentence seems simple enough, but it can be downright confusing.
Essentially, it means that the MDE utility must be able to read a certain
version of the VBA source code, even if there's a VBA password placed on the
VBA Project because the project is locked for viewing. Opening the project
for viewing by using the password when prompted allows the MDE utility
access to the VBA code.
A VBA password on the modules can prevent the MDE utility from creating an
MDE database file. I write "can prevent" this because the behavior is
inconsistent across versions of Access and across service packs. Your
mileage will vary.
> I do have a backup of the database, so I am working
> on that now.
That's one of the marks of a professional. Good luck.
HTH.
Gunny
See http://www.QBuilt.com for all your database needs.
See http://www.Access.QBuilt.com for Microsoft Access tips.
(Please remove ZERO_SPAM from my reply E-mail address, so that a message
will be forwarded to me.)
"altan" <altan@discussions.microsoft.com> wrote in message
news:75296AC4-073B-4B63-A9C5-270300C70CA6@microsoft.com...
> Hi Gunny
>
> Thank you for taking the time to give me some input on my problem.
>
> Firstly, sorry about the spelling of Access, it was just a typing error.
> Secondly, I am not a true novice in designing databases, I don't use the
> wizards, and I do design my own code for the database. However, I
acknowledge
> that I do not know everything and I do not have your experience.
>
> I work with Office XP and do use Microsoft Office XP Developers Edition
> (Legally). I have developed a number of databases for companies that are
in
> use.
>
> So back to my problem. When I want to create the MDE file before packaging
> the product, the Make MDE file selection is not enabled on the Tools,
> Database Utilies menu. On going through to the help on this matter, it
tells
> me
>
> "Some restrictions may prevent you from saving your Access database as an
> MDE file:
>
> 1. You must have password access to the Visual Basic code. "
>
> So as soon as I enter a password for access to the Visual Basic code, then
> the menu item is enabled and I can create the MDE file.
>
> Am I really reading and understanding this incorrectly? What am I doing
wrong?
>
> So all I have done in this database is forget my password. I was stupid
not
> to have written it down. I do have a backup of the database, so I am
working
> on that now.
>
> I would really appreciate you giving me an answer again, no matter how
cruel.
>
> Thanking you
>
> "'69 Camaro" wrote:
>
> > Hi.
> >
> > First, this is not the answer you are seeking.
> >
> > While this is a great place to ask questions, seek advice, and discuss
> > Microsoft Access security, this is the wrong place to ask how to break
into
> > an Access database. None of the experts who regularly post messages
here
> > advise their own paying clients on how to break Access security, so you
> > can't reasonably expect them to give you free advice on how to do so.
> >
> > > > Then secured my vba with a password so that I could
> > > > create an MDE file.
> >
> > There is never a need to place a VBA password on the VBA Project in
order to
> > create an MDE database file.
> >
> > > I would really appreciate any thoughts on this.
> >
> > I doubt this, but since you ask:
> >
> > This next part is going to sound cruel because, well, it _is_ cruel.
The
> > general perception is that anyone who would place a VBA password on an
> > Access database is such a novice that at least 95% of his database was
> > automatically created by the built-in Access Wizards, and at least 90%
of
> > his code was automatically inserted by the Access Control Wizards and
pasted
> > in from code found in the Access Developers Handbook (or other Access
books,
> > or in Access Help, or easily found on the Internet), and could therefore
be
> > recreated by any professional Access developer in minutes (regardless of
how
> > long it actually took the first developer to build the database
> > application). The general perception is that it would be good practice
for
> > such a novice to redo his work and learn the importance of backups and
> > making contingency plans in case disaster strikes, because it often does
> > when one is least prepared for it.
> >
> > Also, you are distributing your product with the Access Runtime, which
means
> > that you are using the Microsoft Office XP Developers Edition. (At
least
> > you are if you intend to distribute copies of the Access Runtime
legally.)
> > This implies that you are passing yourself off to your customers as a
> > professional Access database developer -- yet you use a VBA password on
your
> > database, and you don't even know how to spell the name of the product.
> > (For the record, Access is spelled with two s's, not one.)
> >
> > Therefore, you aren't likely to get much assistance from professional
Access
> > database developers, which is why no one seems to be answering your plea
for
> > help.
> >
> > Remember, in times like these GIYF:
> >
> >
http://www.google.com/search?hl=en&q=Microsoft+Access+VBA+Password&btnG=Google+Search
> >
> > HTH.
> >
> > Gunny
> >
> > See http://www.QBuilt.com for all your database needs.
> > See http://www.Access.QBuilt.com for Microsoft Access tips.
> >
> > (Please remove ZERO_SPAM from my reply E-mail address, so that a message
> > will be forwarded to me.)
> >
> >
> > "altan" <altan@discussions.microsoft.com> wrote in message
> > news:6EEE183F-28BF-46A1-B995-A444CE1944CF@microsoft.com...
> > > This is not a reply, but a SOS. Please, please, is there anyone out
there
> > > that can help me with this problem. I really need to get into my code
> > without
> > > having to redo everything. I do not have any USER ID or passwords set
up.
> > The
> > > only password I have is on the VBA side.
> > >
> > > I would really appreciate any thoughts on this.
> > > Many thanks
> > > altan
> > >
> > > "altan" wrote:
> > >
> > > > I split my database. Then secured my vba with a password so that I
could
> > > > create an MDE file. My product is distributed as a XP run-time
product.
> > > > However, I have now forgotten the password and cannot get into the
VBA
> > > > section. Is there a way that I can get the password or bypass the
> > password?
> >
> >
> >
- Next message: '69 Camaro: "Re: DB Compact causes loss of Windows file permissions"
- Previous message: Jean: "DB Compact causes loss of Windows file permissions"
- In reply to: altan: "Re: Acces VBA Password"
- Next in thread: altan: "Re: Acces VBA Password"
- Reply: altan: "Re: Acces VBA Password"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
