Heenan, Lambert
Lambert.Heenan at chartisinsurance.com
Tue Dec 1 09:33:18 CST 2009
I just did that to my back end. Made no difference at all. I still get the symptoms I described earlier: "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." This is while working directly in the back end, with no front end open or attached. Lambert -----Original Message----- From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Max Wanadoo Sent: Tuesday, December 01, 2009 9:46 AM To: Access Developers discussion and problem solving Subject: Re: [AccessD] Access XP (2002) - unknown function name date() I suggest you compact/repair the BE with the FE closed, then relink the FE. Max On 01/12/2009, jwcolby <jwcolby at colbyconsulting.com> wrote: > 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