Please trust me that there is a good case for having 2 tables due to the
fact that there are a lot of functionality already built on top of the
existing table and practically speaking it is the only way to avoid mistakes
in this important part of the system.
However, I do want to share some of the existing functionality (forms
reports etc.) and I wonder if anyone can help me as I described in my
initial email
Thank you,
Samuel
"RBear3" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
>I would agree with Joseph. Normalization rules would suggest that this
>data should be in one combined table with a separate field to help filter.
>A good example of this is "Employees" all in one table with an "inactive"
>checkbox to allow you to pull only active or inactive.
>
> --
> Hope that helps!
>
> RBear3
> .
>
> "Samuel" <(E-Mail Removed)> wrote in message
> news:(E-Mail Removed)...
>> The tables are identical in structure but they are used for 2 different
>> types of data
>>
>>
>> "RBear3" <(E-Mail Removed)> wrote in message
>> news:(E-Mail Removed)...
>>> Why do you have two "absolutely identical tables"? There is no valid
>>> reason for this in a normalized relational database.
>>>
>>> Delete one table and you should be all set.
>>>
>>> --
>>> Hope that helps!
>>>
>>> RBear3
>>> .
>>>
>>> "Samuel" <(E-Mail Removed)> wrote in message
>>> news:eWxgQ%(E-Mail Removed)...
>>>>I have 2 tables which are absolutely identical
>>>>
>>>> On top of these tables I have forms, queries and reports
>>>>
>>>> I am looking for a method that I can use one version of the above for
>>>> both tables
>>>>
>>>> Specifically is it possible to set the source of a report at runtime,
>>>> how can I set a variable within a form before opening it so that will
>>>> be the basis of all the rest
>>>>
>>>> Thank you,
>>>> Samuel
>>>>
>>>>
>>>>
>>>
>>>
>>
>>
>
>
|