Doug Murphy
dw-murphy at cox.net
Mon Jun 19 15:53:22 CDT 2006
No external references. The runAccess.exe takes care of the problem of the runtime setting the last version of Access opened on the machine as the default. This is than handy thing MS sets so that if you have two versions of Access on a computer it will always try to open the next db in the version that was last run. Just looked in the object brower and NZ is part of the application object so it should be there if the application opens. I'll keep looking. Doug -----Original Message----- From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Charlotte Foust Sent: Monday, June 19, 2006 1:43 PM To: Access Developers discussion and problem solving Subject: Re: [AccessD] NZ problems in runtime Sounds like a broken reference on the target machine. Where are you storing the runtime files and are you calling the MSAccess runtime or the RunAccess.exe that you get with the installer? We eliminated some problems by using RunAccess.exe, but I don't remember offhand what they were. Does your app interact with any of the other Office apps or use any of their libraries? If you don't have exactly the same service packs installed, that can cause the problem, as can different versions of the MDAC libraries. Charlotte Foust -----Original Message----- From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Doug Murphy Sent: Monday, June 19, 2006 1:28 PM To: 'Access Developers discussion and problem solving' Subject: [AccessD] NZ problems in runtime Hello Group, I just had a client we shipped an AccessXP runtime to contact us with a problem. The error indicates that Access does not recognize the NZ function which is being used in an append query to insure that nulls are not inserted into a field. This is the first report we have had of this error. We use Wise 9 and Sagekey scripts for Access 2002. I am getting the clients computer configuration so I can set up a test system and try to duplicate the error. My original understanding was that it was a new computer with XP pro on it. The application runs fine on my development machine. Any suggestions. Thank you in advance. Doug -- AccessD mailing list AccessD at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/accessd Website: http://www.databaseadvisors.com -- AccessD mailing list AccessD at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/accessd Website: http://www.databaseadvisors.com