(E-Mail Removed) wrote:
> Ultimately I would like to put in the loan officers name and the
> phone, city state and log in id auto fill the rest of the form so I
> don't have to type it each time.
> the interface we use is a basic access name, log in id, phone, city,
> state fields, type of problem text box--resolution text box and a few
> buttons to start new call, close this call--
I doubt if you want to store this data with each record. What you do is
have a separate table with that information. When you input the loan
officer's ID (name, number or whatever) a link to a loanofficer table
retrieves that data to display it on the form, but should not store it
anywhere else.
Consider that if you store the data in each record and then if the data
changes, for example a new telephone number or address, then you may need to
edit hundreds or thousands of records to get them all updated. With a
linked (parent-child) table, you make one change and everything is changed.
Take a look at the Northwind sample database. It has examples of parent
child tables and relationships.
>
> "Joseph Meehan" <(E-Mail Removed)> wrote in message
> news:0bBdh.2276$(E-Mail Removed)...
>> (E-Mail Removed) wrote:
>>> Is there a way to have an autofill option?
>>> if I enter data in 1 field can it cross reference previous database
>>> entries and autofill the other predefined fields?
>>>
>>> Thank you
>>> Andrew
>>
>> It is difficult to tell exactly what you want to do. It should be
>> possible, but it may be undesirable.
>>
>> If you are filling in data based on a formula and then saving it,
>> you are saving redundant data. Normally you would not save that
>> data, but retrieve or re-compute it any time you needed it. Access
>> usually will work faster and more reliably when you don't store
>> redundant data. --
>> Joseph Meehan
>>
>> Dia 's Muire duit
--
Joseph Meehan
Dia 's Muire duit