Date box misbehaving after migration to SQL Server

[ExcessionOCP]

Hi All,



I'm hoping someone can help me here because I'm tearing my hair out.

I have migrated my backend to SQL and everything was fine, until I tried out a particular form which has two date controls on, "DateofPurchase" and "DeliveryDate". There is some code behind the form that takes the month value of these dates and does some maths to decided some other things.

The issue is that my code has started failing with a type mismatch when I try to read the value of the "Delivery Date" field.

When I debug.print the typename of each control, the working one shows as "Accessfield" but the non working one shows as "Text Box". Trying to debug.print the control value errors with a type mismatch

The data type in the SQL backend is set to "Date" for both colums.

I cannot for the life of me work out what has happened - does anyone have any ideas?

Thanks in advance.

[Minty]

If you open the linked table in design view what datatype does Access think they are?

[ExcessionOCP]

If you open the linked table in design view what datatype does Access think they are?

My god you are a genius! Access thought it was "Date Time Extended" but a quick refresh of the link has sorted that and it works fine now! I changed the date type in the DB ages ago but Access must have been holding on to it.

THANK YOU!!

[Minty]

My god you are a genius! Access thought it was "Date Time Extended" but a quick refresh of the link has sorted that and it works fine now! I changed the date type in the DB ages ago but Access must have been holding on to it.

THANK YOU!!

Glad it you sorted it. Unlike Access linked tables, it doesn't pick up design changes to SQL tables without a refresh of the link.