DWUTKA at marlow.com
DWUTKA at marlow.com
Fri Feb 20 18:25:02 CST 2004
Sorry, use 97 for almost all of my backends....so I keep forgetting about the Unicode issue! <grin> However, what are you LINKING the records in that table with? Each record, in a one per question table, would need a caller ID (Long), Question Number (could be byte), then the answer (another byte). Now you have 6 bytes per answer (instead of 1 in ASCII, or 2 in Unicode!) Drew -----Original Message----- From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com]On Behalf Of Stuart McLachlan Sent: Friday, February 20, 2004 6:15 PM To: Access Developers discussion and problem solving Subject: RE: [AccessD] Table Structure questions On 20 Feb 2004 at 17:49, DWUTKA at marlow.com wrote: > > Instead of have a record per question, why not store all of the answers in 1 > record. The easiest method would be to just create a string, of the > answers. (12012111002211000). Question 1 would be mid([MyField],1,1) > Question 2 would be Mid([MyField],2,1), and so on. > > That does 2 things for you. One record a call, will knock quite a bit of > storage space, and by using a string, instead of Long values, you are only > using 1 byte per question + 1 extra byte per call, instead of 4 bytes for > each question. > Aren't strings stored in A2K onwards as Unicode ie two bytes per character? Storing the answers as 25 separate Byte fields takes up less space (even if it is only one byte per character + 1 extra) and saves all that string manipulation. -- Lexacorp Ltd http://www.lexacorp.com.pg Information Technology Consultancy, Software Development,System Support. _______________________________________________ AccessD mailing list AccessD at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/accessd Website: http://www.databaseadvisors.com