I created a church database in Access 97 that contain the typical Name,
Address, and Phone Number information fields. I had a number of
different reports to print query data in different formats.
I had a number of textboxes in the report designs that used the trim()
function to suppress printing of leading spaces. As an example, one of
the textboxes had the following:
=Trim([Address])
Basically, this is looking for a situation where someone accidentally
created spaces at the beginning of the address field and the report
suppresses the leading spaces for appearances. All the textboxes used
the trim() function which include some boxes that concatenated several
fields together.
The problem is that when the database were moved to two other computers,
one worked correctly; the other one didn't.
One system is XP, the other is 2000. Both are running identical version
of Access 2002 (10.4302.4219) SP-2. The database was converted to Access
2002 file format by the Windows 2000 system and works correctly. The XP
version does not; it apparently thinks 'trim()' is a variable and
requests an input value from the user. The two databases are identical
(byte for byte). The options for Access on the two systems are
identical.
I suspect that something is not loaded correctly or not loaded at all on
the XP system but I don't know where to look. I thought I should have
some of idea of what the real problem is before I blindly reload Access
on the XP system.
Any ideas would be greatly appreciated.
Thanks,
Dave
********************************
Dave Bovey
de*****@netzero.com
********************************