G
Guest
We are experiencing a problem with our Access code on only XP machines
running Office XP. We are developing in Access 2000 and have a new PC
running XP Service patch 2 and Office XP Service Pack 3.
We are experiencing problems with the VBA Reference even though the Visual
Basic for Applications is a selected referenced. One example is with
CHR$(13). When we right click to find the definition, it cannot find it?
The error we receive is:
“Function is not available in expressions in query expression
‘[tblCustomers].[Address1] & “,†& Chr$(13) & Chr$(10) &
[tblCustomers].[City] & “,†&[tblCustomers].[State] & “,†&
[tblCustomers].[ZipCode] & “,†& Chr$(13) & Chr$(10) &
[tblCustomers].[Phone]’.â€
We have reviewed the references many times. The main difference we can see
is that previous version has a reference of Microsoft Access 9.0 Object
Library vs. Microsoft Access 10.0 Object Library on the newer machine.
However, we are at a loss as to why this should be a problem as the issue is
with a VBA Reference.
The VBE6.DLL we are using on both machines is the identical version.
We are at a loss on why these definitions are not working and would like to
see if anyone else has any ideas?
running Office XP. We are developing in Access 2000 and have a new PC
running XP Service patch 2 and Office XP Service Pack 3.
We are experiencing problems with the VBA Reference even though the Visual
Basic for Applications is a selected referenced. One example is with
CHR$(13). When we right click to find the definition, it cannot find it?
The error we receive is:
“Function is not available in expressions in query expression
‘[tblCustomers].[Address1] & “,†& Chr$(13) & Chr$(10) &
[tblCustomers].[City] & “,†&[tblCustomers].[State] & “,†&
[tblCustomers].[ZipCode] & “,†& Chr$(13) & Chr$(10) &
[tblCustomers].[Phone]’.â€
We have reviewed the references many times. The main difference we can see
is that previous version has a reference of Microsoft Access 9.0 Object
Library vs. Microsoft Access 10.0 Object Library on the newer machine.
However, we are at a loss as to why this should be a problem as the issue is
with a VBA Reference.
The VBE6.DLL we are using on both machines is the identical version.
We are at a loss on why these definitions are not working and would like to
see if anyone else has any ideas?