Tol version compatibility

[Lander Ibarra Iriondo]

Please compile the following code lines in Tol and SqlServer. You will find
a TERRIBLE situation, I did it with last SnapShot version downloaded yesterday from
web page.
Curiosly I haven´t any problem with the SnapShot(Aug 24 2004) which returns
ONLY AN OBJECT WITH THE SAME
NAME!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
but compiling wtiht the last Snap I have THREE COMPLETLY DIFERENT OBJECTS and
TWO OF THEM WITH THE SAME NAME!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
We can´t to run any estimation, forecasting project using the last Snap
version.

Just do it.

-- Sql Code
drop table emuDatos02
drop table emuDatos01

create table emuDatos01
(
nombre varchar(100),
descripcion char(200)
constraint emuDatos01Pk primary key(nombre)
)
create table emuDatos02
(
nombre varchar(100),
fecha datetime,
valor float,
constraint emuDatos02NomFk foreign key(nombre)

references emuDatos01,

constraint emuDatos02Pk primary key(nombre, fecha)
)
insert into emuDatos01 values ('Nombre01', 'Nombre 01');
insert into emuDatos02 values ('Nombre01', '20040101', 1);
insert into emuDatos02 values ('Nombre01 ', '20040102', 2);
insert into emuDatos02 values ('Nombre01', '20040103', 3);

TOL Code
Real DBOpen(MyAlias, MyUser, MyPassword);
Text Query =
"

select nombre, fecha, valor
from emuDatos02
order by nombre, fecha

";
Set Set00 = DBTable(Query);
Set Set01 = DBSeriesColumn(Query, C, ?);
Real DBClose(MyAlias);

[manuelb]

The problem was a wrong behaviour of DBGetText in the old ODBC driver.

Before the new native drivers were created, every Text field (CHAR, VARCHAR, etc.)
would hace the last spaces cut out no matter what.

Now only DBSeries, DBSeriesTable and DBSeriesColumn will have the old
behaviour, changes are already on the cvs.