Information not showing on report

[ali3n8]

I have a form that I created which has field called date. I also have another field called followup. In the follow up field i entered an expression to autmatically insert a date three month from what is contained in the date field. I am using this code =DateAdd("m",3,[Date]). My issue is I have created a report called followup so I can pull each records followup date. The problem is on this report its does not show the information contained in the follow up field I am kind of stumped why it is not working. I used this same function in access 2003. I am now using 2007 and it seems like it is not working. Any information would be appreciated if you need more info just let me know.

[Scott Price]

Many of us here are successfully resisting the urge to upgrade to A2007 at least until the first (for me, it'll be the second) service pack comes out to fix known and hitherto undiscovered bugs.

Here is an excellent link to Allen Browne's website with a discussion of the good, the bad, the ugly and the bugs... I don't know whether what you are experiencing is a bug per se, or just an incompatibility issue, but if it works in A2003, and not in A2007 it has to be one or the other.

http://allenbrowne.com/Access2007.html#Bugs

Regards,
Scott

[ali3n8]

That was the issue, didnt find any info in it. But once I saved my db in 2003 format and then opened it on my machine that actually has access 2003 the dates appeared.

[missinglinq]

Also, if your field is actually named Date you need to change it to something else such as OriginalDate or DDate or anything but Date! Sooner or later it's going to cause you grief. Date is a reserved word and a very dangerous one to mess with! Read Reserved Words in Access, Especially Date and Time to learn why.

Linq ;0)>

[Scott Price]

Good catch, Linq! Just musing... I'm wondering if this has something to do with the original inability of A2007 to show the dateadd?? Ali3n8: an interesting experiment would be to rename the field to something like MyDate, then try running it through A2007 again.

Regards,
Scott

[missinglinq]

Another thought: missing reference? I don't know what library DateDiff() resides in, do you?

Linq ;0)>

[Scott Price]

Another thought: missing reference? I don't know what library DateDiff() resides in, do you?

Linq ;0)>

It's part of the Visual Basic Runtime Library for VB6, and I'm sure it's part of the Visual Basic for Applications Library for VBA in A2003.

A2007's advertising says that it works seamlessly with earlier VBA references, however it does have a new Jet DB engine, and does claim also to work with SQL Server...

It is interesting in researching this a little more, the DateAdd() function of VBA can be 'upsized' to the DATEADD() function in SQL Server, with the caveat that they aren't exactly equivalent. It appears the differences have to do with the sub-references rather than the actual function: i.e. the following are supposed to be essquivalence: SQL Server:

DATEADD(hh,5,getdate()) 

Access VBA:

DATEADD(hh,5,Date())

I'm now wondering if A2007 is trying to convert the DateAdd of VBA to the DATEADD of SQL Server, and in doing so is mis-reading the arguments of the function?

Regards,
Scott