Multiple problems with access on this computer

[Heidi]

Ok, I guess both good news and bad - I got the "T". So good that my outlook
isn't a problem, bad that we're still on the search.... What should I try
next?

The first test, when we looked to see if anything "isBroken",
didn't tell us that anything was broken, and the application
works ok on other PC's, so now we are looking for something
subtle.

most have laptops w/Win XP and at least Outlook 2003 if
a couple still have desktops w/Win XP, Office/Outlook XP.

This could be the subtle thing we are looking for: Perhaps it
is an Office 2003 application, not an Office XP application,
or, your application has a reference to Outlook, and perhaps
it works on computers with Outlook 2003, but not with Outlook
XP.

First, let's test if it really is an MDE. Load the application,
press [ctl][G] to take you to the immediate window. Type
this in and press [return] (you may not be able to paste):

?codedb.Properties("mde")

If you get "T", then your application is an MDE. If not then
you will probably need to get a computer with Office 2003.

(david)

Ok - on our network most have laptops w/Win XP and at least Outlook 2003 if
not Office as well (I'm assuming since normally you buy the whole package), 1
or two have desktops with this as well, and a couple still have desktops
w/Win XP, Office/Outlook XP. Mine is the latter. I dont know whether or not
he MDAC will find the same things becasue I'm not the administrator and don't
have access to other people's computers especially since they are laptops. I
may be able to ask our tech to run it but again w/laptops I'm not sure it's
most feasible request...

I'm pretty sure it's the full version of Access - I'm in the middle of
creating another db (w/out modules however) and have not had any problems
yet. Of course, this is an MDB...

I tried to go into the references section but ran into a bit of a snag b/c
the orig file that i'm having problems with won't let me into the module
("global code") because it's an MDE, so I can't recreate it or check the
references from the other one.... Unless I'm just missing something and they
should be standard?

 

[david epsom dot com dot au]

"T" means that it really is an MDE, so the fact that
you can't get into the forms and reports is not down
to some other problem. Next let's see what version it
thinks it is:

Open the application, type [ctrl][g], and into the
immediate window type

?codedb.version

and

?application.CodeProject.FileFormat

and

?syscmd(acsyscmdaccessver)

The first gives you the database file format, the
second gives you the format of the codeproject inside
that file, and the third (just for reference) give you
the version of Access you are using.

You won't be able to copy and paste those into the
window: the unbelievably irritating VBA environment
makes you type the stuff in.

(david)

PS: I'm glad you saw the last message: it never made
it back to my computer. Some kind of strange news
server anomaly.

Ok, I guess both good news and bad - I got the "T". So good that my
outlook
isn't a problem, bad that we're still on the search.... What should I try
next?

The first test, when we looked to see if anything "isBroken",
didn't tell us that anything was broken, and the application
works ok on other PC's, so now we are looking for something
subtle.

most have laptops w/Win XP and at least Outlook 2003 if
a couple still have desktops w/Win XP, Office/Outlook XP.

This could be the subtle thing we are looking for: Perhaps it
is an Office 2003 application, not an Office XP application,
or, your application has a reference to Outlook, and perhaps
it works on computers with Outlook 2003, but not with Outlook
XP.

First, let's test if it really is an MDE. Load the application,
press [ctl][G] to take you to the immediate window. Type
this in and press [return] (you may not be able to paste):

?codedb.Properties("mde")

If you get "T", then your application is an MDE. If not then
you will probably need to get a computer with Office 2003.

(david)

Ok - on our network most have laptops w/Win XP and at least Outlook
2003 if
not Office as well (I'm assuming since normally you buy the whole package), 1
or two have desktops with this as well, and a couple still have
desktops
w/Win XP, Office/Outlook XP. Mine is the latter. I dont know whether or not
he MDAC will find the same things becasue I'm not the administrator and don't
have access to other people's computers especially since they are
laptops. I
may be able to ask our tech to run it but again w/laptops I'm not sure it's
most feasible request...

I'm pretty sure it's the full version of Access - I'm in the middle of
creating another db (w/out modules however) and have not had any
problems
yet. Of course, this is an MDB...

I tried to go into the references section but ran into a bit of a snag
b/c
the orig file that i'm having problems with won't let me into the
module
("global code") because it's an MDE, so I can't recreate it or check
the
references from the other one.... Unless I'm just missing something and they
should be standard?