MartyConnelly
martyconnelly at shaw.ca
Sat May 22 13:12:31 CDT 2004
This is actually all documented by Microsoft. This was an online book for a couple of years on the MS Site but then some bright light at Microsoft pulled it. Probably because it was out of date or out of print, who knows what machinations go on there. Appendix A Specifications "Microsoft Jet Database Engine Programmer's Guide from Microsoft Press" I believe there are two editions I have edition one 1995 ISBN 1556158777 For example queries number of tables 32 number of fields in recordset 255 number of fields in order by clause 10 number of nested queries 50 number of chars in parameter name 255 number of ANDS in an expression 40 number of chars in SQL statement 64,000 John W. Colby wrote: >>I think I will go off right now and test what error I see when I >> >> >intentionally try and save a record with more than 2K record size. > >And the answer is.... drum roll.... 4240 bytes in A2K - (16 fields x 255 >characters) + (1 field x 160 characters) > >John W. Colby >www.ColbyConsulting.com > >-----Original Message----- >From: accessd-bounces at databaseadvisors.com >[mailto:accessd-bounces at databaseadvisors.com]On Behalf Of John W. Colby >Sent: Friday, May 21, 2004 7:54 PM >To: Access Developers discussion and problem solving >Subject: RE: [AccessD] On DB Bloat, Bad DB Design, and various > > >You know, that's fascinating. I typically set the field size to 255 and >forget it. The person can enter whatever length they need in Address1, >Address2, last name, first name etc. Of course I use memo fields for the >paragraph length tomes that are sometimes needed. I have never seen (to my >knowledge) a failure to write the data. I think I will go off right now and >test what error I see when I intentionally try and save a record with more >than 2K record size. > >John W. Colby >www.ColbyConsulting.com > >-----Original Message----- >From: accessd-bounces at databaseadvisors.com >[mailto:accessd-bounces at databaseadvisors.com]On Behalf Of Jürgen Welz >Sent: Friday, May 21, 2004 2:02 PM >To: accessd at databaseadvisors.com >Subject: RE: [AccessD] On DB Bloat, Bad DB Design, and various > > >"Unnecessary" size restrictions on fields ensure that a record can be saved. > If you have more than 8 text fields at 255 characters per field, Access >will refuse to save the record. Have you forgotten the the 2k character >limit on record size in mdb files? > >Ciao >Jürgen Welz >Edmonton, Alberta >jwelz at hotmail.com > > > > > > > >>From: DWUTKA at marlow.com >> >>Actually I think that talking about Access training/experience is a valid >>topic. >> >>Recently, I have helped a friend with his Access 'homework' from his MIS >>course. I worked cheap (for beer <grin>), but it just kills me what they >>are having students do. The 'instructions' for the assignments has them >>naming tables with spaces, setting unnecessary size limitations for text >>fields, etc. Just plain ugly. In fact one instruction was so goofy, I >>completely bypassed what they were trying to do, and wrote some VBA to have >>the same result. >> >>It is just flat out amazing that the world moves as it does. <grin> >> >>Drew >> >> > >_________________________________________________________________ >MSN Premium includes powerful parental controls and get 2 months FREE* >http://join.msn.com/?pgmarket=en-ca&page=byoa/prem&xAPID=1994&DI=1034&SU=htt >p://hotmail.com/enca&HL=Market_MSNIS_Taglines > >-- >_______________________________________________ >AccessD mailing list >AccessD at databaseadvisors.com >http://databaseadvisors.com/mailman/listinfo/accessd >Website: http://www.databaseadvisors.com > > > >-- >_______________________________________________ >AccessD mailing list >AccessD at databaseadvisors.com >http://databaseadvisors.com/mailman/listinfo/accessd >Website: http://www.databaseadvisors.com > > > > > -- Marty Connelly Victoria, B.C. Canada