Trouble Creating ACCDE file

[Gus Kernot]

I am converting an Access XP application to 2007.

I am having a similar problem to the one mentioned above but my code compiles when I run Debug>Compile.

I have had to go through the code and change various Recordset declarations to DAO.Recordset and I wonder if there may be some problem with one of the libraries.

I could believe there is a problem with an upgrade to one of the libraries but cannot locate any problems manually.

Any hints would be much appreciated as this is a bit of a mystery.

Thanks
Gus



lastjackal1 wrote:

You are right, the code cleanup was the problem in converting to MDE or ACCDE.
24-Nov-09

You are right, the code cleanup was the problem in converting to MDE or ACCDE
The "DoCmd.ShowToolbar "Ribbon", acToolbarNo" does eliminate the QAT. Thank
Albert!

Albert D. Kallal wrote:

Previous Posts In This Thread:

Disable/Hide Quick Access Toolbar
I need to secure an access database, that is control what users can get t
(tables etc.). The database will be in 2007, so I cannot use user leve
control. I tried making the database an MDE, but this failed due to too man
Table IDs. I disabled the following: special keys, display navigation pane
allow full menus and allow shortcut menus. Here is the problem, the Quic
Access Toolbar still allows users to get into the database settings and thu
they can enable all these items again. I cannot find a way to disable tha
pesky Quick Access Toolbar. I tried code using application.setoption, but
could not find a property to disable this. This is a big hole in securit
that keeps me from being able to distribute a database with confidence tha
users can see only what I want them too.

It is VERY VERY VERY VERY VERY unlikely you exceeded the limits here withtoo
It is VERY VERY VERY VERY VERY unlikely you exceeded the limits here wit
too may table id's

Before you do anything like trying to create a accDE (you cannot create mde'
in 2007, they are called accDE), you need to open up any code window, and d
a debug compile

If you find any compile errors, then this means two thing

1) great, it would be HORRIBLE to attempt to distribute your applicatio
with error

2) once you remove the compile errors, you be able to create the accDE (mde
without any trouble at all..


You can customize what goes into that QAT

On the other hand, are you going to provide custom ribbons, or do you pla
to hide the ribbon

Providing custom ribbons is a GREAT way to hide the access interface

However, if you want to hide office button QAT and all ribbons, you ca
place this in your startup form's on-load event

DoCmd.ShowToolbar "Ribbon", acToolbarN

The above hides QAT, ribbon, and office button...

-
Albert D. Kallal (Access MVP
Edmonton, Alberta Canad
(e-mail address removed)

You are right, the code cleanup was the problem in converting to MDE or ACCDE.
You are right, the code cleanup was the problem in converting to MDE or ACCDE
The "DoCmd.ShowToolbar "Ribbon", acToolbarNo" does eliminate the QAT. Thank
Albert!

Albert D. Kallal wrote:


Submitted via EggHeadCafe - Software Developer Portal of Choice
C# And The Little Iterator That Could
http://www.eggheadcafe.com/tutorial...32-0ae26adaa533/c-and-the-little-iterato.aspx

 

[Arvin Meyer [MVP]]

There is no reason that you cannot use and MDB or MDE in Access 2007 or
2010. Unless you are using newer features available only in the latest
version, it is advisable to use the Access 2000 format which can be run in
EVERY version from 2000 on.

 

[David W. Fenton]

Gus Kernot wrote in

I am converting an Access XP application to 2007.

There was no version of Access called "Access XP." There *was* a
version of Office called Office XP, but the version of Access in it
was called Access 2002. I will assume that's the version you mean,
though it makes little difference.

I am having a similar problem to the one mentioned above but my
code compiles when I run Debug>Compile.

I have had to go through the code and change various Recordset
declarations to DAO.Recordset and I wonder if there may be some
problem with one of the libraries.

Sounds like you have references to both DAO and ADO. If you're not
using ADO (and you likely shouldn't be), then get rid of the
reference to it. It's unclear to me why an upgrade would cause this
problem, since upgrading does not add an ADO or DAO reference where
one did not previously exist. This suggests to me that your original
database was not compilable, either.

I could believe there is a problem with an upgrade to one of the
libraries but cannot locate any problems manually.

Any hints would be much appreciated as this is a bit of a mystery.

Have you tried creating an MDE of the original in Access 2002? My
bet is that you'll get a host of compile errors, and those have just
been carried through in the upgrade to ACCDB. If you never compile,
you'll not see the errors, but creating an ACCDE or MDE compiles the
code and you'll not be able to finish that process until the code
compiles.

There may be other factors involved, and this may not apply to you,
but I've seen this quite often -- I find it shocking that regular
users of Access who are writing VBA code do not compile regularly. I
do it ever few lines of code. It's how I make sure MY APP WORKS!