I want to create a recordset from a dbf (dbase IV) file using SQL with a
group by statement. Is this possible?
I receive a strange error message, saying that (translated from dutch) the
selected setting of the sorting sequence is not supported by the operating
system, and that I need to change the settings for the CollatingSequence for
Paradox in the registry. I did this, following the instructions, but it
didn't help, I continue to receive the same error message.
Even without the group by statement, I get the error, using this SQL:
SELECT [temp].FID FROM [temp];
I need this group by statement, because I need to know the number of unique
values and the min and max value in the field FID.
cannot convert between unicode and non-unicode string data types ...Cindy, I have the same problem, there is a solution, In the OLE DB Destination component, in the Mappings option in the input column you must choose the Data Conversion., and that's it. ... I am converting a simple (at least in the SQL Server 2000 DTS days) to this ...error message stays the same ... numerous times I have inserted the transformation task between the oracle... (microsoft.public.sqlserver.dts)
Re: SQL Timeout Error ..."Robert Lakinski" wrote: ... but you can access data in Sql server via MS ... I don't know why I got the error message.... (microsoft.public.sqlserver.server)
Re: Multilingual versions of SQL Express 2005 available ? Where ? ... The error code alone is not sufficient. ... error code which is represented in the parameters used to format the SQL...language is used. ... > we may consider provide localized error message according to the error ... (microsoft.public.sqlserver.setup)
Re: cannot convert between unicode and non-unicode data types ... product can't actually produce a meaningful error message.... oracle and the sql database.... Tried dumping to a raw file but the output is still unicode when I try to ... (microsoft.public.sqlserver.dts)
Re: update query ODBC--call failed ... Google results from searching for your error message,... on the local server SQL database.... reporting the error rather than the "ODbc Driver For SQL Server"... (microsoft.public.access.queries)
