Access DB has become troublesome - Please try to help!

=?Utf-8?B?RnJlZA==?= wrote in
:

I keep hearing about "decompile" but what you said here is the
cloest I've seen to a "how to".

Tony Toews gave you very good links on this that explain the whole
process and give detailed instructions.

--
David W. Fenton http://www.dfenton.com/
usenet at dfenton dot com http://www.dfenton.com/DFA/

David,

I could play *Devil's Advocate* here but you are correct. And 99% of the
time I say plit no matter what. However, and here's the Devil's Advocate*
part... I have a Client that backs up twice a day and only one person ever
uses it he says splitting is a not needed and I find it hard to argue with
him. True, he would lose one days worth of data but so far, knock on wood,
nothing has ever happened.

--
Gina Whipp
2010 Microsoft MVP (Access)

"I feel I have been denied critical, need to know, information!" - Tremors
II

http://www.regina-whipp.com/index_files/TipList.htm

"David W. Fenton" wrote in message
36.82...
"Gina Whipp" wrote in
:

If the database is accessed by more then one person at a time then
it should be split

I would argue that if the database is going to be run in A2007
sometimes, it would be better for it to be split even if only one
person ever uses it, because that insulates the data tables from any
problems that might occur in the VBA project when opened in A2007.
It would be easy enough to have code that relinks to a data file in
the same folder as the front end so there'd never have to be any
manual relinking.

--
David W. Fenton http://www.dfenton.com/
usenet at dfenton dot com http://www.dfenton.com/DFA/

Check out this article by Michael Kaplan:

The real deal on the /Decompile switch
http://www.trigeminal.com/usenet/usenet004.asp?1033

If you have multiple versions of Access installed on the same machine, then
you cannot simply click on Start | Run and enter: msaccess /decompile
The reason is that Windows will start the first version of msaccess.exe that
it finds, which may not be the correct version. In that case, create
decompile shortcuts, named appropriately (for example "A2003 Decompile") that
includes the full path to msaccess.exe plus the /decompile switch. You do not
need to include the path to the .mdb file itself (as Tony's shortcut example
suggests), because the very next database that you open with such a shortcut
will have its P code removed. Just remember to hold down the Shift key when
using this special shortcut. Then compact with Shift key, and re-compile your
code.


Tom Wickerath
Microsoft Access MVP
http://www.accessmvp.com/TWickerath/
__________________________________________

"Fred" wrote:

Tom,

Thanks,

I keep hearing about "decompile" but what you said here is the cloest I've
seen to a "how to".

I understand code behind forms, but otherwise (despite lots of reading,
buying the wrong books etc. trying to learn fundamental code things like
this) I really don't understand what a "code module" is or how to start one.


Sincerely,

Fred

I really don't understand what a "code module" is or how to start one.

I used the term "code module" to mean code behind a form or report (aka
"class module"), or a stand-alone module. In Access 2003, you can click on
the Modules tab, and then click on New to create a new empty "code module".
By the way, when you create a new module, you should see those two very
important words "Option Explicit". If you only see this:

Option Compare Database

then check out my "gem tip":

Always Use Option Explicit
http://www.access.qbuilt.com/html/ge...tml#VBEOptions


Access MVP Crystal has some VBA tutorials you might find useful:

http://www.accessmvp.com/Strive4Peace/Index.htm


Tom Wickerath
Microsoft Access MVP
http://www.accessmvp.com/TWickerath/
__________________________________________

"Fred" wrote:

Tom,

Thanks,

I keep hearing about "decompile" but what you said here is the cloest I've
seen to a "how to".

I understand code behind forms, but otherwise (despite lots of reading,
buying the wrong books etc. trying to learn fundamental code things like
this) I really don't understand what a "code module" is or how to start one.


Sincerely,

Fred

Again, thank you everybody.

So far the "new DB and import the objects" seems to have worked. Adn your
pointing me to that made me realize that there is a way to import whole
bunches of them, and with automatically retaining their original names and
relationships. Basically making it about 20 times easier than I though it
was.

And for all of the good and taken advice in the other areas.

Answering the one question, I'm using the tabbed form as sort of a tabbed
switchboard. It seems like a nice idea. I think that if there are
advantages compared to splitting a "switchboard" up between multiple forms
they a

- Only one form to deal with
- Navigation to all of the "subforms" is automatically visible from all
"subforms" without having to be put into all of them.
- Slightly faster switch.

On Tue, 12 Jan 2010 16:29:09 -0500, "Gina Whipp"
wrote:

I could play *Devil's Advocate* here but you are correct. And 99% of the
time I say plit no matter what. However, and here's the Devil's Advocate*
part... I have a Client that backs up twice a day and only one person ever
uses it he says splitting is a not needed and I find it hard to argue with
him. True, he would lose one days worth of data but so far, knock on wood,
nothing has ever happened.

But Gina, with the free handy-dandy J Street Access Relinker, you can
get all the advantages of a split database with none of the hassles!
(Wow, I'm sounding like an infomercial here

It's great for single user scenarios, because it has a mode that
silently and automatically relinks to a BE database if it's in the
same folder as the FE application. I think that takes care of the
devil's 1%.

It's on the J Street Downloads page at http://ow.ly/M56Q.

Cheers,

Armen Stein
Microsoft Access MVP
www.JStreetTech.com

Armen,

I will have to look into that AND perhaps it will convince my Client!

--
Gina Whipp
2010 Microsoft MVP (Access)

"I feel I have been denied critical, need to know, information!" - Tremors
II

http://www.regina-whipp.com/index_files/TipList.htm

"Armen Stein" wrote in message
...
On Tue, 12 Jan 2010 16:29:09 -0500, "Gina Whipp"
wrote:

I could play *Devil's Advocate* here but you are correct. And 99% of the
time I say plit no matter what. However, and here's the Devil's Advocate*
part... I have a Client that backs up twice a day and only one person
ever
uses it he says splitting is a not needed and I find it hard to argue with
him. True, he would lose one days worth of data but so far, knock on
wood,
nothing has ever happened.

But Gina, with the free handy-dandy J Street Access Relinker, you can
get all the advantages of a split database with none of the hassles!
(Wow, I'm sounding like an infomercial here

It's great for single user scenarios, because it has a mode that
silently and automatically relinks to a BE database if it's in the
same folder as the FE application. I think that takes care of the
devil's 1%.

It's on the J Street Downloads page at http://ow.ly/M56Q.

Cheers,

Armen Stein
Microsoft Access MVP
www.JStreetTech.com

"Gina Whipp" wrote in
:

I could play *Devil's Advocate* here but you are correct. And 99%
of the time I say plit no matter what. However, and here's the
Devil's Advocate* part... I have a Client that backs up twice a
day and only one person ever uses it he says splitting is a not
needed and I find it hard to argue with him. True, he would lose
one days worth of data but so far, knock on wood, nothing has ever
happened.

If the OP were always opening it in the same version of Access, I
wouldn't suggest splitting, either. Since he *is* doing that, and
has encountered problems after doing so, it seems to me that
splitting would be prudent.

--
David W. Fenton http://www.dfenton.com/
usenet at dfenton dot com http://www.dfenton.com/DFA/

David,

True and did you see Armen's response? I need to take a look at that
software.

--
Gina Whipp
2010 Microsoft MVP (Access)

"I feel I have been denied critical, need to know, information!" - Tremors
II

http://www.regina-whipp.com/index_files/TipList.htm

"David W. Fenton" wrote in message
36.93...
"Gina Whipp" wrote in
:

I could play *Devil's Advocate* here but you are correct. And 99%
of the time I say plit no matter what. However, and here's the
Devil's Advocate* part... I have a Client that backs up twice a
day and only one person ever uses it he says splitting is a not
needed and I find it hard to argue with him. True, he would lose
one days worth of data but so far, knock on wood, nothing has ever
happened.

If the OP were always opening it in the same version of Access, I
wouldn't suggest splitting, either. Since he *is* doing that, and
has encountered problems after doing so, it seems to me that
splitting would be prudent.

--
David W. Fenton http://www.dfenton.com/
usenet at dfenton dot com http://www.dfenton.com/DFA/

"Gina Whipp" wrote in
:

True and did you see Armen's response?

Yes, but I have never looked at his relinker, because I use my own:

http://dfenton.com/DFA/download/Access/Reconnect.html

I wouldn't bother with that for something like this, since the idea
I suggested was to do the relinking automatically on the assumption
that the back end would be in the same folder as the front end.
Obviously, one could make that conditional, checking if the back end
is in the same folder and relinking if so, and popping up the
relinking dialog if not. But the OP doesn't really need anything
that complicated, I suspect.

--
David W. Fenton http://www.dfenton.com/
usenet at dfenton dot com http://www.dfenton.com/DFA/