Problem with Standard Functions

[Mark A. Sam]

Hello,

I have an app that has been running for years on a client site, using .mde
databases for the front end. Recenlty, one machine at a time, there is a
problem with a screen which I traced to functions in a query, specifically
the Format() and Datediff() functions, giving me an unknown function error
when I try to open the query.

I thought the problem may be that they were Dell Laptops, becuase they seem
to have a lot of problems with Access, but a user has a new Dell Desktop
installed woth Office 2003, and this probleme occured. The other machines
are running Access 2002.

As the machines acted up I removed library references which initially
resolved the issue, but then the problem reoccured on particular machines.
Here are the Libraries now selected:

Visual Basic for Applications
Microsoft Access 10.0 Object Library
Microsoft DAO 3.51 Object Library

in that order.

I get no compile errors on the troubled machines.

I copied a .mdb version onto the network for them to use which resolves the
issue, but leaves the Db open to theft, which happened this winter by a
former employee.

Anyone have any idea on how to resolve this?

Thanks for any help and God Bless,

Mark A. Sam

 

[Douglas J Steele]

Are they all sharing the same database, Mark? It's especially important that
the database be split into a front end (containing the queries, forms,
reports, macros and modules) and a back end (containing the tables and
relationships), and that each user have his/her own copy of the front-end
(preferably on their hard drive) when you're in a non-heterogenous
environment such as you're describing.

This is because when users have different versions of software installed,
it's almost guaranteed that there are going to be problems with the
References collection.

 

[Mark A. Sam]

Hello Doug,

Are they all sharing the same database, Mark?

Yes they are.

It's especially important that

the database be split into a front end (containing the queries, forms,
reports, macros and modules) and a back end (containing the tables and
relationships),

It is.

and that each user have his/her own copy of the front-end

(preferably on their hard drive) when you're in a non-heterogenous
environment such as you're describing.

I think I tested that on one of the machines, but will again when the users
are off.

This is because when users have different versions of software installed,
it's almost guaranteed that there are going to be problems with the
References collection.

Thanks for that information. I'll let you know if running from a local
machine works, but I kind of doubt it, becuase even with the mixed
inviroment in the past, the app ran fine and suddenly didn't.

 

[Douglas J Steele]

Hello Doug,

I think I tested that on one of the machines, but will again when the users
are off.

Thanks for that information. I'll let you know if running from a local
machine works, but I kind of doubt it, becuase even with the mixed
inviroment in the past, the app ran fine and suddenly didn't.

Installing new software can cause problems with References.

 

[Mark A. Sam]

Thanks for your replies Doug. I tried copying the .mdb to the desktop of
the new machine, and then creating the .mde from that and it worked. So I
will try it on the other problem machines. This isn't convenient but it'll
do for now.

God Bless,

Mark

 

[TC]

Maybe this is this relevant:

Once last year, I converted an MDB from a lower version of Access to a
higher one, and then created an MDE in that higher version. The MDE
worked fine on that PC. So I added it to my installation package, and
burned the first 100 CDs for that product.

All of those CDs were bad. On investigation, it seems that the PC where
I did the conversion, had added a reference to Office Web Components:
OWC 10, or somesuch, to the converted MDB. And naturally that reference
carried through to the MDE. The MDE worked fine on that PC, but not on
any of the client PCs, because they did not have that component!

I've no idea why this happened, because I've never used OWC, in that
database or any other!

So the lesson that I learned, was this: after converting an mdb and/or
creating an mde, RE-CHECK ALL THE REFRENCES, just in case they have
been messed with!

HTH,
TC [MVP Access]

 

[Albert D.Kallal]

Microsoft DAO 3.51 Object Library

That should be dao 3.6.....3.5 is for access 97 applications....

 

[Mark A. Sam]

TC,

The Web components library was a problem, and removing it solved this
initiall but then it returned on other machines. I initiated an
autoshutdown program, which is not allowing some apps to close becuase they
get hungup in error dialogs.

God Bless,

Mark

 

[Mark A. Sam]

Thank you Albert,

That solved it. I created a new database recently and imported the objects
into it. Access must have used the 3.51 by default and I didn't notice.

God Bless,

Mark