dBASE SQL Servers - Memo fields and MS SQL Server

Author

Memo fields and MS SQL Server

Trevor

2005-07-08, 3:23 am

Hi All

I need to create some memo fields in MS SQL server. I am using TEXT
fields (longvarchar) for this purpose but when I try to browse the table
I end up with "Database Engine Error: Invalid BLOB handle in record
buffer." I have checked out Jamie Grants excellent article on MS SQL
Server and he touches on this problem but I don't really understand how
to implement his "third option"

//Quote from Jamie's Article:

That leaves us with a third option, which is to create a SHORTDESCR
field in the table. It can be similar to a VARCHAR(50) field, and it
will store the first 50 characters of the actual TEXT field every time
the note is changed and saved. (This can be done with dBase code or
with a trigger on the SQL Server, but that's an article for another
time.) It may not seem ideal, but it does provide a fix for the Blob
error and a performance boost since VARCHARS can be extracted and used
more quickly than TEXT fields

//endquote

Thanks for any help.

Regards
Trevor

*Lysander*

2005-07-08, 3:23 am

In article <MPG. 1d38c40d538da5289896
82@news.dbase.com>,=20
trannnospam@mpxnospa
m.com.noauspam says...
> Hi All
>=20
> I need to create some memo fields in MS SQL server. I am using TEXT=20
> fields (longvarchar) for this purpose but when I try to browse the table=
=20
> I end up with "Database Engine Error: Invalid BLOB handle in record=20
> buffer."=20

Hmmmm...
sounds like the same problem that some people reported with Firebird,=20
although until now I did never see it myself.
I believe the solution was to "unlink" an editor object from its memo-
field before saving/updatinng the table and to "relink" it back after=20
the changes are committed.

By unlinking the editor-object, it will keep its latest "value". So you=20
can save it then to the database.

Maybe you will try if this can help you?

--=20
ciao,
Andr=E9
~~~~~~~~~~~~~~~~~~~~
~~~~~~~~~~~~~~~~~~~~
~~~~~~~~~~~~~~~~~~~~
~~~~~~~~~
Deutsche dBase-Konferenz dBKon 2005 ::: 11. bis 13. November 2005
Deutschsprachige Konferenz zu dBase und anderen Datenbanken
Info: www.dbase-konferenz.de

Jamie A. Grant

2005-07-08, 7:23 am

Hi Trevor. The third option that I mentioned is simpler than it may seem.
If I have a TEXT field called DESCRIPTION, I create VARCHAR field beside it
called SHORTDESCR. Whenever I save to the main Description field, I also
save the first 50-odd characters to the ShortDescr field. It's isn't too
fancy but it works quite well for our software.

In our software, we also remove any HTML formatting or end-of-line
characters that the dBase memo field may have added. That allows the
ShortDescr to display in a grid without weird symbols.

Thanks for the compliment regarding my article. For other readers, the
article reference is: http://www.jpmartel.com/bu18_a.htm

Jamie A. Grant
AV-Base Systems Inc.

Trevor Rann

2005-07-10, 3:23 am

In article <zG3Veh6gFHA.1760@news-server>, jamie_grant@av-
basesystems.com says...
> Hi Trevor. The third option that I mentioned is simpler than it may seem.
> If I have a TEXT field called DESCRIPTION, I create VARCHAR field beside it
> called SHORTDESCR. Whenever I save to the main Description field, I also
> save the first 50-odd characters to the ShortDescr field. It's isn't too
> fancy but it works quite well for our software.
>
> In our software, we also remove any HTML formatting or end-of-line
> characters that the dBase memo field may have added. That allows the
> ShortDescr to display in a grid without weird symbols.
>
> Thanks for the compliment regarding my article. For other readers, the
> article reference is: http://www.jpmartel.com/bu18_a.htm
>
> Jamie A. Grant
> AV-Base Systems Inc.
>
>
>
Thanks Jamie & André
So if I understand correctly, datalinks are the problem. As long as I
don't datalink anything to a SQL text field I should be fine?

Thanks again
Trevor

Sponsored Links