Text field contents cause Access Runtime Crash.

  • Thread starter Thread starter Ron Kunce
  • Start date Start date
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?
 
No, it is an .adp/ade application using OLEdb connections, not ODBC, unless
there is some kind of interaction between them that I am not aware of.
 
Hello Ron:
You wrote in conference microsoft.public.access.adp.sqlserver on Wed, 28
Jul 2004 15:33:22 -0500:

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

RK> Has anyone had any experience with this quirk? Is there a fix?

I would open a support incident with Microsoft.

Also, the number 1500 resembles MTU limit.


Vadim
 
Back
Top