Sage 100

It looks like you have an ODBC connection called MSDASQL that the linked server in SQL is using to pull the data. have you verified that is working? Maybe a password was changed? 

1. Open ODBC Data Source Administrator in Windows
2. Select MSDASQL 
3. Click the Debug tab and click on test connection.

It's just one file.  The other 6 they pull are working fine.

It looks like you have an ODBC connection called MSDASQL that the linked server in SQL is using to pull the data. have you verified that is working? Maybe a password was changed? 

1. Open ODBC Data Source Administrator in Windows
2. Select MSDASQL 
3. Click the Debug tab and click on test connection.

Does the error come up immediately or after some time has elapsed?

Maybe it is choking on a bad record, or a record with a bad date?

It's just one file.  The other 6 they pull are working fine.

It looks like you have an ODBC connection called MSDASQL that the linked server in SQL is using to pull the data. have you verified that is working? Maybe a password was changed? 

1. Open ODBC Data Source Administrator in Windows
2. Select MSDASQL 
3. Click the Debug tab and click on test connection.

It took a while. We ran a Crystal report using the file and didn't have any issues, but maybe the files are read differently?

Does the error come up immediately or after some time has elapsed?

Maybe it is choking on a bad record, or a record with a bad date?

It's just one file.  The other 6 they pull are working fine.

It looks like you have an ODBC connection called MSDASQL that the linked server in SQL is using to pull the data. have you verified that is working? Maybe a password was changed? 

1. Open ODBC Data Source Administrator in Windows
2. Select MSDASQL 
3. Click the Debug tab and click on test connection.

SQL won't accept malformed dates or dates earlier than 1/1/1753...

It took a while. We ran a Crystal report using the file and didn't have any issues, but maybe the files are read differently?

Does the error come up immediately or after some time has elapsed?

Maybe it is choking on a bad record, or a record with a bad date?

It's just one file.  The other 6 they pull are working fine.

It looks like you have an ODBC connection called MSDASQL that the linked server in SQL is using to pull the data. have you verified that is working? Maybe a password was changed? 

1. Open ODBC Data Source Administrator in Windows
2. Select MSDASQL 
3. Click the Debug tab and click on test connection.

Oh, I'm pretty sure they weren't using Sage back then...

SQL won't accept malformed dates or dates earlier than 1/1/1753...

It took a while. We ran a Crystal report using the file and didn't have any issues, but maybe the files are read differently?

Does the error come up immediately or after some time has elapsed?

Maybe it is choking on a bad record, or a record with a bad date?

It's just one file.  The other 6 they pull are working fine.

It looks like you have an ODBC connection called MSDASQL that the linked server in SQL is using to pull the data. have you verified that is working? Maybe a password was changed? 

1. Open ODBC Data Source Administrator in Windows
2. Select MSDASQL 
3. Click the Debug tab and click on test connection.

Hi, Beth. 

Did you try running the checkdate utility?

Oh, I'm pretty sure they weren't using Sage back then...

SQL won't accept malformed dates or dates earlier than 1/1/1753...

It took a while. We ran a Crystal report using the file and didn't have any issues, but maybe the files are read differently?

Does the error come up immediately or after some time has elapsed?

Maybe it is choking on a bad record, or a record with a bad date?

It's just one file.  The other 6 they pull are working fine.

It looks like you have an ODBC connection called MSDASQL that the linked server in SQL is using to pull the data. have you verified that is working? Maybe a password was changed? 

1. Open ODBC Data Source Administrator in Windows
2. Select MSDASQL 
3. Click the Debug tab and click on test connection.

Could it be a data type issue?  (Like text too big to fit into a SQL string column, or big number that is larger than a SQL numeric column allows...).

@Beth Bowers - Has this been resolved?

Could it be a data type issue?  (Like text too big to fit into a SQL string column, or big number that is larger than a SQL numeric column allows...).