|
|
Posted by Erland Sommarskog on 10/30/05 01:44
Neil (nospam@nospam.net) writes:
> OK, point well taken. I don't see any workaround, though, since I'm
> using ODBC linked tables. I can't use a pass-through query and pass the
> table name as a parameter, because pass-throughs return read-only sets.
> And a view wouldn't be able to return just the records for that
> machine.
As for how to sort out the linked tables, you will have to ask in an
Access newsgroup.
> Here's an idea. What if there were one table, but a series of views, with
> each view returning records for a particular unique ID. When the app is
> opened, it's assigned an available ID and its link is set to the view that
> returns records for that ID. Still kind of a kludge, but perhaps a little
> better.
A table-valued function with the machine name as parameter would be better.
But without knowing Access, I'm quite sure that this can be solved by
adding the machine name on the Access side as well. After all, that is
also an RDBMS, and should be fitted for relational solutions.
--
Erland Sommarskog, SQL Server MVP, esquel@sommarskog.se
Books Online for SQL Server SP3 at
http://www.microsoft.com/sql/techinfo/productdoc/2000/books.asp
Navigation:
[Reply to this message]
|