Re: Access apps with user definable fields?
- From: "Amy Blankenship" <Amy_nospam@xxxxxxxxxxxxxxxxxxxxxx>
- Date: Sun, 15 Jan 2006 17:08:55 -0600
<user@xxxxxxxxxxxxxx> wrote in message
news:u2hHxUiGGHA.1032@xxxxxxxxxxxxxxxxxxxxxxx
> Duane Hookom wrote:
>> I have never seen this type of functionality in an Access application. I
>> guess I have never seen an application that needs to allow users to
>> define new fields. New fields would need to added to tables, queries,
>> forms, reports,...
>>
>> This raises a red flag regarding your application design. It might be
>> justifiable but I can't see it.
>>
> I saw this concept it in a nice contacts manager software from Australia
> http://www.biztechsoftware.com.au/
>
> Their forms are not built in Access forms but the data is stored in an
> MDB.
>
>
>
> In this app - from Australia, there is a very nice capability to add new
> fields you want and even remove standard fields you don't. The changes
> result in changes to the table definition. They have some kind of list
> controlled form where they show all fields in user defined sequence in 3-5
> columns on the form. Of course they have their own built in report writer
> so impact on queries and reports isn't so great. Of course you could
> define queries to select all/* fields allowing dynamic contents in the
> table.
>
> It seems fairly common for contacts management types of apps to have
> varying field requirements. Most I have seen use the user definable field
> approach where the user definable fields already exist.
>
> I have an app I built for nonprofits (provided for FREE)who provide FREE
> food, clothes and financial assistance such as prescriptions and to avoid
> utility cutoff, etc. I have it installed in 8 locations. Every user has
> new field requirements. Much of the data is only accessed via online
> forms.
>
> So adding fields by user, causing the table to be modified and providing a
> way to show them on the form would be great for me. Instead what I now do
> is add new fields that others won't mind that for really unique fields, I
> add control switches to control whether certain fields are displayed or
> not.
>
> Hopefully that clarifies where I got the idea and why it appeals to me.
I once had a database design where I had an "objects" table and a
"parameters" table. The parameters table defined everything about the
object, including what type of object it was. A setup like this allows
pretty much infinite flexibility with the data, but might require some fancy
footwork with the SQL.
HTH;
Amy
.
- References:
- Access apps with user definable fields?
- From: user
- Re: Access apps with user definable fields?
- From: Duane Hookom
- Re: Access apps with user definable fields?
- From: user
- Access apps with user definable fields?
- Prev by Date: Re: move record...
- Next by Date: Re: move record...
- Previous by thread: Re: Access apps with user definable fields?
- Next by thread: Re: null recordset
- Index(es):
Relevant Pages
|
