Wortz, Charles
CWortz at tea.state.tx.us
Fri Apr 11 12:02:47 CDT 2003
Myke, You may want to look at the user's memo fields and see if you can do some normalization on them. I had a user that was putting a lot of data into memo fields. But once I analyzed the data I saw that over 90% of them represented only about twelve different values. I added a new status field for those 12 values and left the memo field for the others. User liked the decimating of the amount of typing required to fill out the form. Charles Wortz Software Development Division Texas Education Agency 1701 N. Congress Ave Austin, TX 78701-1494 512-463-9493 CWortz at tea.state.tx.us -----Original Message----- From: Myke Myers [mailto:mmmtbig at bellsouth.net] Sent: Friday 2003 Apr 11 11:45 To: accessd at databaseadvisors.com; dba-sqlserver at databaseadvisors.com Subject: [dba-SQLServer]Access ADP Error I upsized an application from an Access FE / BE to an Access ADP FE / Sql Server 2000 BE. A memo field for Notes became a 'ntext' field in Sql Server. A user is getting a message 'The text is too long to be edited' when she clicks into the Notes field in several records -- records with a lot of data stored in the Notes field. My understanding is that the Sql Server 'ntext' field is limited only by the storage of the server, so I'm guessing that the problem is with the Access Adp FE. Does an Access Adp textbox have a limit on the amount of data it can hold? All suggestions welcome. TIA, Myke _______________________________________________ dba-SQLServer mailing list dba-SQLServer at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/dba-sqlserver http://www.databaseadvisors.com _______________________________________________ dba-SQLServer mailing list dba-SQLServer at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/dba-sqlserver http://www.databaseadvisors.com