Did you check to see if you DSN setup is pointing to the correct version of 100?

Yes the user dsn is pointing to correct version of Sage 100. And v2021 is on a new server. Thank you.

I should add that testing the connection works fine and it pulls in all the tables. I do have the odbc pvxodbc.log when I tried to create a crystal report report. One of the odd things is that it says userid is HPI however I didn't use that user id to log into the SOTAMAS90 datasource in crystal. I used my user id.

Driver version: 4.40.0005
ISAMOpen: UserID='administrator', length=13
GetAccessibleTables:<table=ALL> Open catalog(s) \\masvr12\sage100\v2021\MAS90 , available 1478 table(s)
ISAMClose
Driver version: 4.40.0005
ISAMOpen: UserID='HPI', length=3
GetAccessibleTables:<table=ALL> Open catalog(s) \\masvr12\sage100\v2021\MAS90 , available 1478 table(s)
<CI_Item> Open file \\masvr12\v2021\sage100\MAS90\MAS_JAA\CIJAA\CI_Item.M4T, maxksz=62
ISAMCloseTable: Closing table CI_Item - 0 file reads, 0 re-reads, 0 writes, 0 removes
CACHE STATS - 0 reads, size 86035456 estimated, 0 used
<CI_Item> Open file \\masvr12\v2021\sage100\MAS90\MAS_JAA\CIJAA\CI_Item.M4T, maxksz=62
ISAMCloseTable: Closing table CI_Item - 0 file reads, 0 re-reads, 0 writes, 0 removes
CACHE STATS - 0 reads, size 86035456 estimated, 0 used

Also assuming you uninstalled and reinstalled Crystal, from the folder under the Sage 100 installation folder, and that didn't work - did you try to pull data through the ODBC Connection into Excel or Access? And you have tried this directly on the server as well?

All the work I've done so far has been on the server and yes tested odbc thru access and same results. I did test a separate non sage small access db in crystal and it pulls in records fine.I'm leaning towards doing the migration again. 

All the work I've done so far has been on the server and yes tested odbc thru access and same results. I did test a separate non sage small access db in crystal and it pulls in records fine.I'm leaning towards doing the migration again. 

I guess that's probably best, if you have ruled out Anti-Virus or other utilities. Did you try connecting from a Win 10 workstation?

My guess is this is Advanced with CS/ODBC enabled?  Make sure you installed the service on the new server, changed the system configuration settings, and that firewalls don't block the port used.

Easy way to check if this applies is by looking at SOTAMAS90's Server tab. 

Custom DSN's probably skip by this tab, but SOTAMAS90 will populate it automatically from the system configuration.