Re: Developer 2000: Why use Object ID instead of Object Name?

Makes perfect sense...thanks for painting the picture.

Russ Whiteman wrote in message <75c3e6$kgu$1_at_news1.inlink.com>...
>Well...in the project I'm working on (a FE for a billing system), we often
>end up having to research a customer.
>Checking to see if there are any related accounts, and in some cases, our
>customers are trying to -hide- that fact, so we need to start looking for
>patterns in the data. The amount of data involved makes a multi-record set
>awkward to use, and it's difficult to query the database in such a way as
to
>pull out only the records you are interested in.
>
>With this need in mind, the simplest way to compare data is to have two (or
>three or six) data forms open at once, so you can see -just- what
>differences and similarities exist. The query can be a very generic form
>(all customers named 'Smith'), which produces a multi-record form that is
>then used to select the records you want complete details on. That detail
>record should not be limited to a single instance.
>
>The first version of the system, implemented in ::cough:: Access, didn't
>have this capability, and it was sorely missed. <g> Actually, the
>situation can be generalized to cover -any- case when you need to compare
>multiple data-sets for whatever reason.
>
>John Haskins <76054.334_at_compuserve.com> wrote in message
><75c01m$r2p$1_at_news-1.news.gte.net>...
>>Just curious: why would you run multiple instances of a form?
>>
>>Thanks.
>>
>>
>>Russ Whiteman wrote in message <75b5gd$751$1_at_news1.inlink.com>...
>>>One example would be if you want to allow multiple instances of a form...
>>>they'll all have the same name, but different ID's. I'm sure there are
>>>other cases (or forms would be the only one that allowed ID's), but
that's
>>>the one I seem to run into the most.
>>>
>
>
>
Received on Fri Dec 18 1998 - 05:10:50 CET