[AccessD] Form system

Higher rate?

The 'end users' for this system don't need to understand databases at
all, which is why I am building this system.

This system requires the following 'knowledge' about the system:

The system is built around 'Root Forms'.  A root form is a 'single' form
'concept'.  Each root form then can have unlimited form revisions.  The
end users who use these forms are creating Form Entries.

So, for example, the form this system was specifically designed for was
a 'Contract Review Form'.  A form revision would be 'A', which would
have the 'design' of the form.  Once Revision A is activated, end users
(who have the appropriate permissions) can click on a button to view or
create/edit a Form Entry, where they can fill out a Contract Review Form
Rev. A form in their browser.  They can save their form at any time (and
also 'save and close'), along with 'locking' their form.  When a form is
locked, the locking user can select who specifically can edit the form
(so if Group A, Group B, User 1 and user 2 can 'create/edit' Contract
Review Forms, if User 1 creates a form entry, User 1 can lock that form
entry and set any group or user with permissions on that form to be able
to edit it in the locked state, so if they select Group A, then only
User 1 and Group A can edit that form entry.)

Also, as far as controls, that is another advantage to web based
interfaces, dynamic controls.  

Searching and tracking of these form entries requires no knowledge of
the database, and that's a good thing, because technically all relevant
data is really only stored in a handful of tables, the rest of the
tables are setup to handle the interface and form designs.

Drew

-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Edward S
Zuris
Sent: Tuesday, April 29, 2008 12:51 PM
To: 'Access Developers discussion and problem solving'
Subject: Re: [AccessD] Form system


 This looks like a more challenging project and 
 should command a higher rate.

 I wrote a system to allow end users how to create
 forms on the fly.  It was hard work and ended up
 using everything as text boxes because there are
 different rules for each of the items to place
 on a form.  

 For example this is how a label was emulated:
    sData = ""
    sData = "=" & Chr$(34) & Trim$([rsData]![zData] & " ") & Chr$(34)

 Though in the end user had to struggle with
 learning various database concepts.
The information contained in this transmission is intended only for the person or entity to which it is addressed and may contain II-VI Proprietary and/or II-VI Business Sensitive material. If you are not the intended recipient, please contact the sender immediately and destroy the material in its entirety, whether electronic or hard copy. You are notified that any review, retransmission, copying, disclosure, dissemination, or other use of, or taking of any action in reliance upon this information by persons or entities other than the intended recipient is prohibited.