Qdabra Database Accelerator

Re: DBXL not “seeing” update to DB settings

Catharine — Fri, 12 Mar 2010 13:53:49 GMT

Sorted !

Thank you all for your thoughts. There was a SQL trigger on my table which was writing a portion of data elsewhere, and the table to be written to needed updating as well.

Catharine

Re: DBXL not “seeing” update to DB settings

Catharine — Fri, 12 Mar 2010 13:40:26 GMT

Hi Jimmy,

I have checked the field that is causing the problem and there are no rules or default values associated with it. The mapping is HUGE... I have sent a copy of the mapping in an email to Ernesto

Here is a bit of the xml...

<IsKey>false</IsKey>

<NodePath>my:Sustain/my:ApplicationSourceLocationGroup/my:ApplicationSourceLocation</NodePath>

<Type>Column</Type>

<ValueType>System.String</ValueType>

<ObjectName>ApplicationSourceLocation</ObjectName>

<Promoted>false</Promoted>

<ColumnType>string</ColumnType>

<Nodes>

<s0:IsVisible>false</s0:IsVisible>

</Nodes>

</NodeMapInfo>

Re: DBXL not “seeing” update to DB settings

Jimmy — Fri, 12 Mar 2010 13:07:20 GMT

Could it be that there's some other field related to the one you think is the problem (either by a rule or a default value) that could be causing the problem? Which field in the form is the one you think is the problem?

Re: DBXL not “seeing” update to DB settings

Jimmy — Fri, 12 Mar 2010 12:58:03 GMT

Might you attach a screenshot of your mapping and of the DB table in this thread?

Re: DBXL not “seeing” update to DB settings

Catharine — Fri, 12 Mar 2010 12:49:15 GMT

Hi Ernesto

Thank you for the prompt reply.

I have edited my doctype. I have removed the field which is giving problems from the mapping. I have re mapped the field and saved. I have reshredded the document.

I still get the error. (I feel as if I am going mad ! - there must be something I am doing wrongly.)

I have the webservice set up to send the dbxl errors to my inbox. I have included one of the emails in my email to you.

Thank you

Catharine.

Re: DBXL not “seeing” update to DB settings

ErnestoM — Fri, 12 Mar 2010 12:16:41 GMT

Hi Catharine,

I'm sorry that you're having issues. Your investigation sounds very complete and it is a strange situation. In our experience, DBXL will pick up these database changes, so I wonder why that's not happening in your case.

You mention that you edited the doctype, clicked refresh database, and then saved. That should've also done the trick.

The next thing I could suggest is to rebind the troublesome field. In the database mapping tab, click the yellow database icon. This will cause the database schema to show in the right taskpane. Double click on the column (the one that changed data types). Then save the doctype. Can you try this and let us know the result?

Throughout this troubleshooting you did, were there any other error or warning messages in eventvwr? Or just the once above (in red)?

DBXL not “seeing” update to DB settings

Catharine — Fri, 12 Mar 2010 12:06:20 GMT

When shredding a document I got the following error

“Message: Caught exception on shredding document (DocType = 'ARKForm', DocId = 796) encountered a critical error and needs attention: System.ApplicationException: An error occurred saving form data to the database: -One of the form's values was too large or could not be converted to the correct data type to be stored in the database.“

I have investigated the document and found that one of the fields contained 280 chars and the field in the DB was set to nvarchar(200).

I am sure I have found the field which is causing the problem, because when I delete the value in the field and save I don’t get any errors.

Also when I reduce the length of the field to 199 characters and save I don’t get any errors. When I have the field with 201 characters I get errors.

I have moved the data to another field on the form – (which is already mapped to a nvarchar(max) field) - and saved, I don’t get errors – so it I don’t think it is a problem with the “total” amount of data shredded.

I have updated the table in the database to be nvarchar(max) and saved. I have taken the field value (280 chars) and pasted it into the db successfully, to check that the field is now big enough.

I still get errors when I shred the document.

I have opened the doctype in dbxl refreshed the database and saved. – still errors

Checked the mapping to make sure that field is not mapped anywhere else. It is not mapped to another field in this table. ( It is mapped to another table the field table was already set to nvarchar(max) and other long fields are mapped to it with no problem.)

After changing the db to be nvarchar(max), reduced the length of the field to 199 characters and saved with no errors. When I increased the field to 201 characters I get the error.

I am sure I am missing a step somewhere but don’t know where.

Thank you

Catharine