Thanks all,
But as I said before, I cannot use a join.
This is because of a quirk of Access that means that adding a simple join to
my already quite complex select statement, the resulting dataset takes ages
and ages to complete. As the MDB I am working with is comes from a third
party I can only read its data I cannot make changes to the way it works,
indexes, table structures or relationships.
A select statement written in Access itself demonstrates the same behaviour
and believe me the select statement is not where the fault lies.
I used to be able to do something like ...
employee.indexname="Primary"
employee.seek "=",112
that is very much cleaner and distinct to me than the 5 lines of code that I
need to execute for each of my master rows.
The above method requires the table to be opened once, closed once, Index
set once and then for each master row I simply need to do a seek and
possibly a NoMatch check (which I would have with whatever method I use).
Am I being advised that this functionality is no longer available?
I don't know what LINQ is I am afraid.
Many thanks all,
jON
"jON Rowlan" <jo*******@hotmail.comwrote in message
news:Oq**************@TK2MSFTNGP06.phx.gbl...
I am slowing get my head around the concept of treating tables as
collections of rows as vb.net seems to prefer.
However, I have an indexed table in an Access database that I want to
scan.
I want to match a certain field but don't want to issue one select
statement
for each row in my master table.
I'd rather connect the table to an object and then use a seek or locate
command to get to the correct row that I want.
I can't use a join because it is really slow and an indexed lookup on a
dbtable would be best.
I can't even work out where to start ...
there don't seem to be any methods to cause a dbtable to locate a record
based upon an index item.
can anyone provide some basic VB that I can research further please?
Many thanks all,
jON