Obviously, you have no idea what you are talking about when it comes to
Access/JET. Nor do you have any idea who you are dealing with when you refer
to me as "kid". I am surely old enough to be your father, with more years
experience in databases than you are old.
Just to make it absolutely clear, everything you have said below is patently
incorrect with the exception of it being inadvisable to use Access (or any
database) with bound records on an air card. That is just as true, btw, if
you use bound forms with a SQL-Server back-end. A stable network, which does
not include anything like aircards, is a requirement for bound datasets.
--
Arvin Meyer, MCP, MVP
http://www.datastrat.com
http://www.mvps.org/access
http://www.accessmvp.com
'unless the design is poort'
or
'there is a vpn requirement'
or
'wireless cards act funny, and Access crashes'
or
'you want to run your database-- as is- a decade from now'
or
'you want to use industry-best tools for optimizing indexes'.
I strongly disagree kid.
It has nothing to do with design.
My network is perfectly stable. I don't have any other large files
that ever crash, no.
Indexing becomes critical.
Of course.. 'Access doesn't really support indexing'.
and 'Access doesnt' really support the proper USAGE of indexing'.
Thanks
