R
Ron Kunce
We have encountered a problem with which we need some expert help. We have
a small number of users with Windows 95 based-PCs using an Access 2000
runtime .ADE application to access data in an SQL Server back-end database.
It seems these users encounter an "invalid command in an unknown module"
error which causes there Access session to crash with a system dump. This
only occurs when they try to open a legal description of a property record
in which the legal description is a SQL Server text field with more than
(approx.) 1500 characters. They have no problem viewing descriptions under
this length but occurs for any and all records when the field value size is
over this limit.
Has anyone had any experience with this quirk? Is there a fix?
a small number of users with Windows 95 based-PCs using an Access 2000
runtime .ADE application to access data in an SQL Server back-end database.
It seems these users encounter an "invalid command in an unknown module"
error which causes there Access session to crash with a system dump. This
only occurs when they try to open a legal description of a property record
in which the legal description is a SQL Server text field with more than
(approx.) 1500 characters. They have no problem viewing descriptions under
this length but occurs for any and all records when the field value size is
over this limit.
Has anyone had any experience with this quirk? Is there a fix?