I have a VB6 application that utilizes SQL-DMO to import a file into a table (ImportData Method is used). However, I receive the following error "Invalid date format @#" when I execute the program.
The issue is, I have a Server X with regional setting for date as dd/mm/yyyy and the Database Server is in the standard mm/dd/yyyy. The Server X produces an error output file of records that previously failed to insert but now I want to import the data. However, the file produced has a date/time format in the previously mentioned dd/mm/yyyy.
Therefore, does anybody know if via SQL-DMO you can set the session date format to DMY instead of MDY? And, will this resolve the date conflict issue?
The issue is, I have a Server X with regional setting for date as dd/mm/yyyy and the Database Server is in the standard mm/dd/yyyy. The Server X produces an error output file of records that previously failed to insert but now I want to import the data. However, the file produced has a date/time format in the previously mentioned dd/mm/yyyy.
Therefore, does anybody know if via SQL-DMO you can set the session date format to DMY instead of MDY? And, will this resolve the date conflict issue?
