[AccessD] Need more than 255 fields! (was - Hit the Wall?)

How about using subforms for each tab page?  That way you could have up to 11 different recordsources.

It sounds like you were able to logically split the FE fields into 11 pages.  It shouldn't be too difficult to at least split the BE into 2 tables.


-----Original Message-----
From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Dan Waters
Sent: Friday, July 23, 2004 2:14 PM
To: 'Access Developers discussion and problem solving'
Subject: RE: [AccessD] Need more than 255 fields! (was - Hit the Wall?)


This sounds good too.

The form is 8" W X 5" tall.  It uses a tabbed control with 11 tabs.  This is a Six Sigma Project management module, within a Workflow System.  I've done many processes like this, and people love it (a direct quote!).  If you compare this approach to managing a business process to using paper forms, emails, memory, phone calls, walking down the hall, 'smoke signals', etc., it's a great productivity tool.  

Some processes, like Debit Memos, or Supplier Deviations, are simple.  Some, like Supplier First Article, Nonconforming Material, or Six Sigma Projects, are complex.  And the more complex, the more value a database has.

I've made the screens very easy to use.  Labels are colored to indicate required, optional, locked, or system entered.  During the current event the focus is moved to the page and the field where the work on that process probably needs to be done next.  Access is great for this kind of stuff where a main goal is to make the user's life much easier.

Dan

-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Michael Brösdorf
Sent: Friday, July 23, 2004 1:59 PM
To: Access Developers discussion and problem solving
Subject: AW: [AccessD] Need more than 255 fields! (was - Hit the Wall?)

How about 2 tables with a 1:1 relationship? To display that as a form you could use an main form/sub form approach or two subforms on an (unbound) main form.

But 270 field - who is gonna read/understand this?? Does that even fit on a standard-size-display?

Michael

-----Ursprüngliche Nachricht-----
Von: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com]Im Auftrag von DWUTKA at marlow.com
Gesendet: Freitag, 23. Juli 2004 20:39
An: accessd at databaseadvisors.com
Betreff: RE: [AccessD] Need more than 255 fields! (was - Hit the Wall?)


Go with an unbound form.  There is no limit to how many properties a Class can have, so build a class to represent a 'record', and fill it with multiple recordsets.

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 1:23 PM
To: Database Advisors
Subject: FW: [AccessD] Need more than 255 fields! (was - Hit the Wall?)


Any other ideas on ways to resolve this issue?

Thanks!
Dan Waters

-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Dan Waters
Sent: Thursday, July 22, 2004 8:45 PM
To: Database Advisors
Subject: [AccessD] Hit the Wall?

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

--

--------------------------------------------------------------------------------------------------------------------
The information in this email may contain confidential information that 
is legally privileged. The information is only for the use of the intended 
recipient(s) named above. If you are not the intended recipient(s), you 
are hereby notified that any disclosure, copying, distribution, or the taking 
of any action in regard to the content of this email is strictly prohibited.  If 
transmission is incorrect, unclear, or incomplete, please notify the sender 
immediately. The authorized recipient(s) of this information is/are prohibited 
from disclosing this information to any other party and is/are required to 
destroy the information after its stated need has been fulfilled.

Any views expressed in this message are those of the individual
sender, except where the sender specifies and with authority,
states them to be the views of Tappe Construction Co.

This footer also confirms that this email message has been scanned
for the presence of computer viruses.Scanning of this message and
addition of this footer is performed by SurfControl E-mail Filter software
in conjunction with virus detection software.