Creating a relationship with a linked table

[Amy]

I am creating a database that is linked to Outlook. This new database has
look-up fields that are drawing their information from Outlook. I have
created a query from the table that is linked to Outlook in order to narrow
the information for the look-up field. This is causing my pc to run very
slowly (only when i am in this db), and the relationship between the table
with the look-up field and the new "Outlook Query" is not shown; but the
look-up fields do work. Any ideas on how to create a better relationship that
will show up on the relationship page and make my pc fast again?

 

[John Vinson]

I am creating a database that is linked to Outlook. This new database has
look-up fields that are drawing their information from Outlook. I have
created a query from the table that is linked to Outlook in order to narrow
the information for the look-up field. This is causing my pc to run very
slowly (only when i am in this db), and the relationship between the table
with the look-up field and the new "Outlook Query" is not shown; but the
look-up fields do work. Any ideas on how to create a better relationship that
will show up on the relationship page and make my pc fast again?

Since Access has absolutely no way to control what can and cannot be entered
into Outlook, and since Access JET database engine indexes don't apply to
Outlook .pst files, I think you're not going to have an easy time doing this!

About all I can suggest is importing the data for the lookup table from
Outlook into an indexed, related Access table on some periodic basis; it may
not be up to the minute accurate, but you'll have to decide on the
appropriate tradeoff between performance and concurrancy. Working across
software platforms it's not yet easy to have both.

 

[dbahooker]

In other words
a) Jet can't enforce Referential Integrity
b) Jet shouldn't be used for anything
c) SQL Server doesn't have a 2gb limit ROFL
d) even if you hit some size limit in SQL Server you can still enforce
cross-database DRI
e) if you do find some limit in DRI in SQL Server; you can use
Triggers-- which gives you about 100 times more control than VBA
f) triggers run even if the end user has 'Macros Disabled'