J
John =?ISO-8859-1?Q?=D8llg=E5rd?= Jensen
Hi,
Using an ADP Access 2003 front end application with SQL Server backend:
An application form is "populated" with several controls (textboxes,
dropdown etc).
Some text fields have recordSource datatype nvarchar, other fields have
datatype ntext.
If "old" data (existing record) in a ntext based field is
corrected/edited and saved (updated) the field data become empty.
nvarchar based fields are working as normal.
Do as follows:
Put cursor in the midle of a word in a ntext based field
Press 'Backspace' for deleting the character to the left og the cursor
position
Enter another character for replacing the old character (entering same
character does not result in the same problem)
Save record (using the standard save-button on an Access form)
Now all data disappears. Data is gone.
Trace:
Data disappears when returning from the before_update handler.
I have tried removing all code from the event-handlers for tracing the
cause of this behaviour, but still data is lost after doing as described.
Any clue for this behaviour?
regards John
Using an ADP Access 2003 front end application with SQL Server backend:
An application form is "populated" with several controls (textboxes,
dropdown etc).
Some text fields have recordSource datatype nvarchar, other fields have
datatype ntext.
If "old" data (existing record) in a ntext based field is
corrected/edited and saved (updated) the field data become empty.
nvarchar based fields are working as normal.
Do as follows:
Put cursor in the midle of a word in a ntext based field
Press 'Backspace' for deleting the character to the left og the cursor
position
Enter another character for replacing the old character (entering same
character does not result in the same problem)
Save record (using the standard save-button on an Access form)
Now all data disappears. Data is gone.
Trace:
Data disappears when returning from the before_update handler.
I have tried removing all code from the event-handlers for tracing the
cause of this behaviour, but still data is lost after doing as described.
Any clue for this behaviour?
regards John