Max Wanadoo
max.wanadoo at gmail.com
Tue Dec 1 10:16:50 CST 2009
If it cannot fund the now() function then that is a library missing problem. Could your problem be a leading space before the now() in the design. I have always put date() in the design and General as type which is equiv of now() but never gives this error. Hth Max -----Original Message----- From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Heenan, Lambert Sent: 01 December 2009 15:29 To: 'Access Developers discussion and problem solving' Subject: Re: [AccessD] Access XP (2002) - unknown function name date() I've seen it where Now() is the default value, which is essentially the same thing. It manifests itself for me occasionally when I open a table is design view in the BE. It will give me an error message: "The expression you entered has a function name that Microsoft Access can't find." Then the weird stuff happens. After opening the table in design mode, if I look at the field that has Now() for the default value there is no default value expression showing up! So I close the table and then immediately open it up again in design view. The field then will display its default value expression [ which is =Now() ] and the error message does not show up. To make Access complain again all I need to do is close the back end and then open it up again. The above symptoms will then recur. I *do not* see any rows with #unknown values however. This is an Access 2002 format MDB file being worked on by Access 2002 SP3. Lambert -----Original Message----- From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of jwcolby Sent: Tuesday, December 01, 2009 9:32 AM To: Access Developers discussion and problem solving Subject: [AccessD] Access XP (2002) - unknown function name date() I am seeing an issue in a linked table where the default value is set to date(). If I view the table it displays #unknown for the value for the field that is supposed to be using date() as the default value - and the function Time as well for that matter. If I go directly in the BE that does not happen, and I can add a new record. So it is only in a linked table that this is an issue. No missing references. SP3 applied. This kinda looks like a missing reference but that is not the case. I am not finding this problem with a Google search. Has anyone seen this problem? -- John W. Colby www.ColbyConsulting.com -- 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