You can look into creating the lookups by modifying the tabledef but this
will be much more trouble than creating forms if your clients are worried
about billing hours.
Another possibility is for you to create views for them. This won't be the
same as the lookup they now have since it won't offer a combo but when they
type a value in the lookup field, the related data will show up in the
query.
"Jon in Canby Or." <JoninCanbyOr[ at ]discussions.microsoft.com> wrote in message
news:8297BA81-7E4E-4061-B8C0-05D66CB98A37[ at ]microsoft.com...
[Quoted Text] > Pat, thanks for responding. I agree with you on the using forms & queries
> etc. and this is the first time I've actually bumped into anyone using the
> Lookup tab like this. The problem is the client designed the database &
> Access app and I was brought in late in the game + I don't know that
> they'll
> pay my or want to develop the stuff themselves when "it worked just fine
> before we upsized and started using SQL Server". I guess I'm looking for a
> simple method to bridge the gap if one exists.
>
> "Pat Hartman(MVP)" wrote:
>
>> Users shouldn't have direct access to tables. The "lookup" is simply a
>> crutch intended for novice users. Once you start using queries and
>> forms,
>> the table level lookup is no longer necessary. They didn't get upsized
>> because this is a Jet only feature. You are probably correct. If the
>> links
>> are deleted, you'll loose the lookups again.
>>
>> The best solution is to create forms for the users. They can be forms in
>> datasheet view so they even look like tables but you'll be able to use
>> queries as their RecordSources (that join the main table to the lookup
>> table) and you'll be able to put edit code in the correct form events.
>>
>> If you don't have referential integrity enforced, it is important to take
>> that step.
>>
>>
>> "Jon in Canby Or." <JoninCanbyOr[ at ]discussions.microsoft.com> wrote in
>> message
>> news:088BB7DB-7E37-42F7-99AA-8B3D51101FFD[ at ]microsoft.com...
>> >I was recently tasked with upsizing an Access db (that I was not
>> >familiar
>> > with) to SQL Server. I used the upsizing wizard to do this having it
>> > create
>> > linked tables. The database extensively uses the Lookup tab properties
>> > of
>> > the
>> > table design to format the table view with combo boxes and checkbox,
>> > etc.
>> > I
>> > don't know if any of them made it across in the upsizing wizard because
>> > I
>> > also implemented a "slick" routine that I got from this newsgroup that
>> > deletes and relinks the tables at startup that doesn't actually work
>> > well
>> > and
>> > that I've pulled the plug on, but the Lookup properties are gone now.
>> > In
>> > the
>> > mean time the users are howling for their combo boxes. I've laboriously
>> > recreated many of them by hand but I'm left to wonder if there isn't /
>> > wasn't
>> > a better way to make sure they all made it to the new database. I keep
>> > getting nagged to recreate this one or that one and I'm worried about
>> > how
>> > stable it'll be. I'm sure if somebody deletes the table and then
>> > relinks
>> > the
>> > table I'll have to recreate all these lookup properties again. Does
>> > anybody
>> > know a better way to manage this?
>>
>>
>>
|