I fail to see the relevance of that statement to what I posted.
I think many issues around here are caused by folk not being able to
differentiate features of the Access 'layer' from those of the Jet
'layer'. Linked tables may indeed be visible in the Access interface
(and may even be extended by it, or perhaps bastardized as happens
with tables, constraints, etc**) but they are a feature of Jet.
In other words, I was just trying to add interest, to raise folks'
overall understanding rather than a straight answer to a straight
question (the latter you'd already done). "Teach a man to fish" and
all that jazz. Yes, I should know better. These newsgroups are more
like the hustings (e.g. "Vote for me", "Rate this as an answer", "Post
50 officially 'Helpful' answer for a silver star" etc) than a wiki.
** I've been accused of being too theoretical, so here's a proof of my
"Access bastardizes Jet tables and constraints" assertion: run this
VBA to create an mdb named 'DropMe.mdb' in your temp folder,
containing a single table with a single column of type _fixed width
text_ with _Unicode compression_ and pattern matching validation via a
_CHECK constraint_, then open it in the Access interface to whether
the features _emphasized_ above are discoverable in the Access
interface without resorting to ADO:
Sub BastardizeTable()
' Kill Environ$("temp") & "\DropMe.mdb"
Dim cat
Set cat = CreateObject("ADOX.Catalog")
With cat
..Create _
"Provider=Microsoft.Jet.OLEDB.4.0;" & _
"Data Source=" & _
Environ$("temp") & "\DropMe.mdb"
With .ActiveConnection
Dim Sql As String
Sql = _
"CREATE TABLE Customers (customer_number" & _
" NCHAR(6) WITH COMPRESSION NOT" & _
" NULL UNIQUE, " & vbCr & "CONSTRAINT customer_number__pattern" & _
" CHECK(customer_number LIKE '[0-9][0-9][0-9][0-9][0-9][0-9]'));"
..Execute Sql
End With
Set .ActiveConnection = Nothing
End With
End Sub
Jamie.
--
