So, I need to allow the use of Import Templates.
They are useful and are available for a reason.
(I think its been posted on the forum that there is no way to programmatically call the import and pass params (validate, add rec if not found, don't delete import file). Or else I could have a program "sniff" the import first, make sure it has readable columns names & data, AND THEN start the import. I know I can do an EXPORT USING to specify a template... but have not tried personally to import with a template. )
But if your user is supposed to import a CSV, and picks the XLS version of the desired file, for some reason it appears Aware is importing "crud" into MSSQL.
THEN, when you try to browse the file just imported, it "just spins" on the grid.
Yes, it would be nice if there was an additional setting on "Import" to select only certain file types, but I don't understand how even 1 record is getting past the column matching and makes its way into the db.
I'm going to have to add a hook to a Stored Procedure to truncate the table when this happens, because the user cannot open the table to browse it and delete rows with multi-select.