Forum Discussion

Minty909's avatar
Minty909
Copper Contributor
Aug 12, 2025

SSMA For Access not recognising DateTime/Extended fields

I have already posted up about this here: https://www.access-programmers.co.uk/forums/threads/ssma-bug-with-date-time-extended-fields.334442/ The current version of SSMA fails to recognise fields s...
access
developer
SSMA
George_Hepworth's avatar
George_Hepworth
Silver Contributor
Aug 12, 2025

I see that you did provide a repro accdb in the other post.

There is no way to add the new, previously defined datatype DateTimeExtended, in SSMA. Maybe there's another workaround, but it sure does look like converting the datatype in Access is the way it will need to be done to support migration, even though SQL Server supports DateTime(2).

 

Minty909's avatar
Minty909
Copper Contributor
Aug 13, 2025

Hi George,

Just for information - I'm using SSMA version 10.2  

The work arounds are fine for smaller projects but on a large migration would be a massive extra workload, especially if you were frequently replacing the data from a live environment during development, assuming you couldn't change the data types in the live system.

  • George_Hepworth's avatar
    George_Hepworth
    Silver Contributor
    Aug 14, 2025

    I have the same version.

    I opened an issue for this missing datatype in the SSMA GitHub, using the Feedback option under Help in SSMA.


    https://github.com/microsoft/SSMA/issues/20

    Perhaps you can add a comment documenting the hurdles you face because of this ommission. I can see how this will become an even bigger issue as more people adopt the DateTimeExtended option. 

     

Resources