Function is not available in expressions . . . .

[AnotherNewGuy]

We've replaced an XP Pro computer running MS Office Pro 2003 with another XP
Pro computer running MS Office Pro 2003. The user is getting "Function is
not available in expressions in query expression 'Trim([LastName]) & ", " &
Trim(FirstName])'" in the app they rely on daily.

I've found the solution where Tools, References is used to reference the
library in the Visual Basic editor, but this is an MDE file, and Visual Basic
is not accessible. The company who wrote the program no longer services it.

Can anyone offer any suggestions at all?

thx . . .

 

[Douglas J. Steele]

Unfortunately, you may be out of luck.

The problem is that Access insists that references be the same version on
the client machines as on the developer's machine, and that they be in the
same location. If, for example, you've installed some software that installs
a newer version (or older, for that martter) of a referneced library, the
References collection can go awry. If you don't have the original MDB file,
you may not be able to determine what files are being referenced, and what
version of each file is required.

 

[Golfinray]

You would have to decompile the MDE file. Google "decompile mde." You will
get a bunch of hits.

 

[AnotherNewGuy]

As I feared. Oddly, the install for MS Office Pro was from the same CDs on
both machines, and we've compared the libraries for version and location.
Both *appear* to be identical.

I've told them they'd probably have to find another solution, but we'll
leave the old machine in place for a while.

thx . . .

Unfortunately, you may be out of luck.

The problem is that Access insists that references be the same version on
the client machines as on the developer's machine, and that they be in the
same location. If, for example, you've installed some software that installs
a newer version (or older, for that martter) of a referneced library, the
References collection can go awry. If you don't have the original MDB file,
you may not be able to determine what files are being referenced, and what
version of each file is required.

--
Doug Steele, Microsoft Access MVP

(no e-mails, please!)

We've replaced an XP Pro computer running MS Office Pro 2003 with another
XP
Pro computer running MS Office Pro 2003. The user is getting "Function is
not available in expressions in query expression 'Trim([LastName]) & ", "
&
Trim(FirstName])'" in the app they rely on daily.

I've found the solution where Tools, References is used to reference the
library in the Visual Basic editor, but this is an MDE file, and Visual
Basic
is not accessible. The company who wrote the program no longer services
it.

Can anyone offer any suggestions at all?

thx . . .

 

[AnotherNewGuy]

Will try. thx

You would have to decompile the MDE file. Google "decompile mde." You will
get a bunch of hits.

We've replaced an XP Pro computer running MS Office Pro 2003 with another XP
Pro computer running MS Office Pro 2003. The user is getting "Function is
not available in expressions in query expression 'Trim([LastName]) & ", " &
Trim(FirstName])'" in the app they rely on daily.

I've found the solution where Tools, References is used to reference the
library in the Visual Basic editor, but this is an MDE file, and Visual Basic
is not accessible. The company who wrote the program no longer services it.

Can anyone offer any suggestions at all?

thx . . .

 

[AnotherNewGuy]

The decompilers I've found all say that VBA modules remain compiled and
locked. Do you know if any will, at least, let us open the VBA editor to get
to references page?

You would have to decompile the MDE file. Google "decompile mde." You will
get a bunch of hits.

We've replaced an XP Pro computer running MS Office Pro 2003 with another XP
Pro computer running MS Office Pro 2003. The user is getting "Function is
not available in expressions in query expression 'Trim([LastName]) & ", " &
Trim(FirstName])'" in the app they rely on daily.

I've found the solution where Tools, References is used to reference the
library in the Visual Basic editor, but this is an MDE file, and Visual Basic
is not accessible. The company who wrote the program no longer services it.

Can anyone offer any suggestions at all?

thx . . .

 

[Douglas J. Steele]

I'm suggesting it could have been some other application, not even
necessarily from Microsoft, that broke the references.

--
Doug Steele, Microsoft Access MVP

(no private e-mails, please)

As I feared. Oddly, the install for MS Office Pro was from the same CDs
on
both machines, and we've compared the libraries for version and location.
Both *appear* to be identical.

I've told them they'd probably have to find another solution, but we'll
leave the old machine in place for a while.

thx . . .

Unfortunately, you may be out of luck.

The problem is that Access insists that references be the same version on
the client machines as on the developer's machine, and that they be in
the
same location. If, for example, you've installed some software that
installs
a newer version (or older, for that martter) of a referneced library, the
References collection can go awry. If you don't have the original MDB
file,
you may not be able to determine what files are being referenced, and
what
version of each file is required.

--
Doug Steele, Microsoft Access MVP

(no e-mails, please!)


message

We've replaced an XP Pro computer running MS Office Pro 2003 with
another
XP
Pro computer running MS Office Pro 2003. The user is getting "Function
is
not available in expressions in query expression 'Trim([LastName]) & ",
"
&
Trim(FirstName])'" in the app they rely on daily.

I've found the solution where Tools, References is used to reference
the
library in the Visual Basic editor, but this is an MDE file, and Visual
Basic
is not accessible. The company who wrote the program no longer
services
it.

Can anyone offer any suggestions at all?

thx . . .

 

[David W. Fenton]

=?Utf-8?B?QW5vdGhlck5ld0d1eQ==?=

I've found the solution where Tools, References is used to
reference the library in the Visual Basic editor, but this is an
MDE file, and Visual Basic is not accessible. The company who
wrote the program no longer services it.

Can anyone offer any suggestions at all?

Can you copy the files to the location referenced in the MDE? You'll
have to register them there, too, or it won't work, I think. This
would mean having duplicate files, but if it makes your app work, I
can't see how that would be something you'd worry about!

 

[AnotherNewGuy]

These are new computers where the app never worked. It still works fine on
their old ones.

I'm planning to compare TLB and OLB files on the two computers today, but I
know I'm grasping at straws.

I'm suggesting it could have been some other application, not even
necessarily from Microsoft, that broke the references.

--
Doug Steele, Microsoft Access MVP

(no private e-mails, please)

As I feared. Oddly, the install for MS Office Pro was from the same CDs
on
both machines, and we've compared the libraries for version and location.
Both *appear* to be identical.

I've told them they'd probably have to find another solution, but we'll
leave the old machine in place for a while.

thx . . .

Unfortunately, you may be out of luck.

The problem is that Access insists that references be the same version on
the client machines as on the developer's machine, and that they be in
the
same location. If, for example, you've installed some software that
installs
a newer version (or older, for that martter) of a referneced library, the
References collection can go awry. If you don't have the original MDB
file,
you may not be able to determine what files are being referenced, and
what
version of each file is required.

--
Doug Steele, Microsoft Access MVP

(no e-mails, please!)


message
We've replaced an XP Pro computer running MS Office Pro 2003 with
another
XP
Pro computer running MS Office Pro 2003. The user is getting "Function
is
not available in expressions in query expression 'Trim([LastName]) & ",
"
&
Trim(FirstName])'" in the app they rely on daily.

I've found the solution where Tools, References is used to reference
the
library in the Visual Basic editor, but this is an MDE file, and Visual
Basic
is not accessible. The company who wrote the program no longer
services
it.

Can anyone offer any suggestions at all?

thx . . .