I am working with a VFP developer to help convert one of their applications.
Everything was going well until I ran into a problem with a cursor returned by a stored procedure.
One of the fields is always a NIL value.
They claim that they have assigned a Varchar(max) value to the field in their stored procedure but Xbase++ will not recognize the type. I think it is a type "text", not supported by Xbase++ and not a type Varchar(max) because Xbase++ is reported that at least one of the field types is "text".
Has anyone dealt with this before?
Who has experience with SQL Server and ODBCDBE?
Who has experience with SQL Server and ODBCDBE?
The eXpress train is coming - and it has more cars.
Re: Who has experience with SQL Server and ODBCDBE?
Hello Roger !
This was done by CursorAdapter-Class in VFP.
I think, Xbase++ should support memo-fields.
I "translate" my VFP-memo-fields into Varchar(max) in $MS-SQL-Server.I think it is a type "text", not supported by Xbase++ and not a type Varchar(max) because Xbase++ is reported that at least one of the field types is "text".
This was done by CursorAdapter-Class in VFP.
I think, Xbase++ should support memo-fields.
Hans-Peter
Re: Who has experience with SQL Server and ODBCDBE?
The only way we could make this work was to change it from Varchar(MAX) to Varchar(500).
I agree that Xbase++ needs to at least support Varchar(MAX), but type Text has been deprecated by Microsoft.
I agree that Xbase++ needs to at least support Varchar(MAX), but type Text has been deprecated by Microsoft.
The eXpress train is coming - and it has more cars.