My company uses an Access project frontend and a SQL Server 2000 backend for one of it's applications.
We have just moved from Access 2000 to Access Runtime 2003, and are currently having a problem with some details disappearing from a Client Contact Log.
Users edit/add entries to the log through an Access form which has a View stored proc as it's Data Source - this simply returns the logs associated with the current client.
The form displays as a Continuous Form, and users can add new log entries or edit existing ones. The data that is disappearing (randomly it seems) is from the detail section (ntext) of the log (other fields are unaffected). One of the most frequent occurances is when spell-check is used.
This also occurs (randomly) when spell-checking letters (ntext).
I was wondering if anyone else had come across similar problems with Runtime versions of Access.
Sorry if I haven't included all the facts.
We have just moved from Access 2000 to Access Runtime 2003, and are currently having a problem with some details disappearing from a Client Contact Log.
Users edit/add entries to the log through an Access form which has a View stored proc as it's Data Source - this simply returns the logs associated with the current client.
The form displays as a Continuous Form, and users can add new log entries or edit existing ones. The data that is disappearing (randomly it seems) is from the detail section (ntext) of the log (other fields are unaffected). One of the most frequent occurances is when spell-check is used.
This also occurs (randomly) when spell-checking letters (ntext).
I was wondering if anyone else had come across similar problems with Runtime versions of Access.
Sorry if I haven't included all the facts.
Last edited:
