Textarea/Memo field issue

[shattuck49]

I have a project using a Microsoft Access database with multiple memo fields. When I try to update the memo fields using a detail view with textarea fields, I get the following error: "Invalid precision value SQL State is: HY104". If I reduce the amount of text in the textarea fields everything works fine (I don't know the exact amount of data where it works/doesn't work) and if I paste all of the text directly into a Access memo field it takes it with no problem. Any ideas why Alpha Five seems to be setting a limit on the amount of text? Thank you.

[Doug Page]

Re: Textarea/Memo field issue

From a simple internet search:

------------------------------------------
HY104 Invalid precision or scale value

The value specified for the argument ColumnSize or DecimalDigits was outside the range of values supported by the data source for a column of the SQL data type specified by the ParameterType argument.
------------------------------------------

This would make me think that there is a number in you code that is going out of range.

[Atta]

Re: Textarea/Memo field issue

I have found out that I would use a field that did not have enough "space".

So I would recommend to make the field longer.

Thanks

[shattuck49]

Re: Textarea/Memo field issue

Still having problem with memo fields. After more testing, I have discovered that if I type the text into the textarea I cannot exceed 255 characters without the abovementioned error when I try to save the record, but if I paste the text into the textarea, I can exceed 255 characters with no problem. I am at a lost as to what is happening here.

[iRadiate]

Re: Textarea/Memo field issue

An old thread, but I ran into this issue last night while entering a fairly lengthy text into a TextArea control.

Although I have the TextArea control bound to a varchar(max) field in my SQL table, I could not insert into the table until the number of characters in the TextArea was reduced from 1268 chars (with spaces) to 1093 chars (with spaces). I don't know exactly where the cutoff lies. This should not be a limitation the the varchar(max) field in the SQL table.

Is there a limitation on the number of characters in a TextArea control?

[Garry Flanigan]

Re: Textarea/Memo field issue

Seems to me you may be doing something in your validation with a variable of type char in xbasic - such data types are limited in size and will not accept string lengths exceeding something like 1024 from memory, even though you mention 1093. Alternatively it may be a function designed to to work with char types.
Anyhow, just a thought that may point you in the right direction.

[iRadiate]

Re: Textarea/Memo field issue

Garry, thanks for the suggestion. I did have validation on the textarea field but even if I turn validation off, the problem still exists.
It seems to be a problem between the textarea character field and the varchar(max) field in my SQL database.
It's actually SQL Server that is throwing the error yet varchar(max) should not be limited afaik.

[drgarytraub]

Re: Textarea/Memo field issue

And this may be relevant too: I get the same error when trying to export a dbf table that contains memo fields to a sql table. If I reduce the size of the memo field to approx 1000, it works. But that is obviously not acceptable because many of the memo fields have way more than 1000 chgaracters. Any insights would be appreciated.

[GGandhi]

Re: Textarea/Memo field issue

if ms sql you may be able to use nText if MySQL then you may be able to use text variable.
check these out.

[-Jinx-]

Re: Textarea/Memo field issue

Try changing your connection string for that particular component to MSSQL 2000

I can't recall exactly why, but I had the same problem and this was the workaround. Anytime I have to input a lot of text I have to use the 2000 connection string to the same DB as my normal one.

[drgarytraub]

Re: Textarea/Memo field issue

Wow Jinx. That works!!

Even though I am using SQL Server 2012, following the recommendation of Jinx above, I created a connection string based on SQL Server 2000, and that works.

Thank you very much

[GGandhi]

Re: Textarea/Memo field issue

even though you got it working, take a look at nText field. it is same as memo in dbf. it stores data in an external location with a pointer to that area. if I recall correct, it can store up to 2gb size.( I am sure you won't need that size)

[iRadiate]

Re: Textarea/Memo field issue

Ghandi,

According to Microsoft, ntext is going to be removed in future SQL versions, so I'm not sure that it would be wise to use that datatype.

I was a little uncertain about changing the string for a UX component as it applies to the whole component and not just the problem field.
But as it also seems to work for Dr. Traub, I might look a this option.

I wonder if this is something worth running by the folks at Alpha?

Thanks guys.

[-Jinx-]

Re: Textarea/Memo field issue

Wow Jinx. That works!!

Even though I am using SQL Server 2012, following the recommendation of Jinx above, I created a connection string based on SQL Server 2000, and that works.

Thank you very much

Glad it worked for you!

Guys,
I looked back through my old emails to see why I originally found out about this fix for the issue and it was within some correspondence with Selwyn about the same problem as above. He told me that it was because my drivers for Microsoft SQL or OBDC on the Server machine that is running the App server needed to be updated. I tried that and it didn't work for me, but it may work for you guys. I'm still running the 2000 connection string for large text fields.

[Anita Headley]

Re: Textarea/Memo field issue

When I tried to create a 2000 connection to my SQLServer 2008 database, I get a message saying SQL Server does not exist or access denied. I copied my 2008 connection which has been working fine except for one UX that tries to send a very long text string back to the database. The database field is typed as varchar(5000), but anything over about 1000 characters blows up with the SQL State is: HY104 error.
My SQLServer 2008 connection is : {A5API='SQLServer',A5DBVersion=2008,Server='(local)',A5ANSINullPadWarn=Default,Trusted_connection=yes,Database='tocas'}

I just changed the 2008 to 2000. That didn't work. Is there something else I need to change?

Alpha 5 newbie