[AccessD] Hit the Wall? (Solved)

Dan,

If speed is not critical, always go for the minimum data size necessary for
to hold the data.  A byte will hold that data quite nicely and double the
number of such fields you can fit in a given amount of memory.  

John W. Colby
www.ColbyConsulting.com 

-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Dan Waters
Sent: Tuesday, July 27, 2004 5:22 PM
To: 'Access Developers discussion and problem solving'
Subject: RE: [AccessD] Hit the Wall? (Solved)


Drew - whatever you get paid - charge more!

This would be pretty slick.  Might be interesting even if I wasn't dealing
with a full table.

Anyway - my customer wants to go to SQL pretty soon, so for now I did a
cheap solution.  Each pair of checkboxes stood for Approved, Disapproved, or
if both were blank then it meant no approval yet.  So, I'm now using a
single integer field where 0 means not yet, 1 means approved, and 2 means
disapproved.  This got me 35 more fields so I should be good to go for a
while.

Thanks to everyone for all your inventive ideas!
Dan

-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of DWUTKA at marlow.com
Sent: Sunday, July 25, 2004 8:45 PM
To: accessd at databaseadvisors.com
Subject: RE: [AccessD] Hit the Wall?

Dan, if you have a lot of yes no fields, you may be able to stick with just
one table!  Instead if using yes/no fields (which take a byte each), I would
go with merging the yes/no fields into a long, or byte field.  With a byte
field, you can get 8 yes/no fields in one field.  With a Long, you can get
31 (32, if you want to have a little math fun).  Use bit comparison for the
yes/no fields.

ie, if a field has 3 as a value, that means that 1 and 2 are turned on, and
nothing else.

So whatever 'value' is represented by 1 can be checked with:

rs.("MyField").value AND 1

Drew

-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com]On Behalf Of Dan Waters
Sent: Friday, July 23, 2004 6:54 AM
To: 'Access Developers discussion and problem solving'
Subject: RE: [AccessD] Hit the Wall?


Michael,

How did you split the table up and apply limits to the width of the query?
Did your form change sources as the users moved from one area to another?

Unfortunately, there is no normalization I can do that would make any sense,
and wouldn't hurt the app.

I didn't know that queries has an 8K limit, but I hope I won't hit that.
Most of the fields are short text fields, or yes/no checkboxes.

Thanks!
Dan

-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Michael Maddison
Sent: Friday, July 23, 2004 12:41 AM
To: Access Developers discussion and problem solving
Subject: RE: [AccessD] Hit the Wall?

No,

We hit this same problem and had to split the table up and apply limits to
the width of the query. Be careful with the 8K row limit as well, you will
likely run out of row space well before 255 columns.

Our client insisted they wanted to scroll sideways over 5 years of data,
displayed monthly with 6 columns per month.  Our prototype had vertical
scrolling but no no no we want it like Excel ;-)))

cheers

Michael M


In an Access app w/FE and BE, I need a table that has about 270 fields. A
single form will be bound to the table.  (This is a business process
management application.)  If I upsize this to a project (never done this), I
can have up to 1024 fields in a table.

 

I tried creating a query to join two smaller tables, but queries are also
limited to 255 columns.

 

Is there a way around this so I can still use an Access BE?

 

Thanks!

Dan Waters

-- 
_______________________________________________
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

-- 
_______________________________________________
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

-- 
_______________________________________________
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com