> Fra: "John Coyle" <[EMAIL PROTECTED]> > > Dag, we've used Access too for various applications over the years, > including an Access 2 program that currently runs in 38 hospitals in our > state, and an Access 95 (became 97) program that manages the maintenance of > our city council's mobile phones and radios assets (over 3000 units). In > all, it's not a bad database system in a single-PC or small network > environment, particularly the later versions, but you do need to construct > it carefully - dragging code over the network is an absolute performance > killer! It's good for end-users who want to put small apps together, but > we've gained a lot of work from them when they realise they've bitten off > more than they can chew! > > We've also used the Jet engine in various apps without problems: in one > instance the database contains many thousands of records in a complex > relational structure, and there were performance issues at first which, like > many, were solved as PC's got faster and had more RAM to play with. > > I don't mind it, in summary - but I wouldn't use it for anything where the > number of records got to the million mark or more.
I agree. See another post, I think I would stop as early as 15-20.000 items in one list. > Somebody said something about using Auto-number fields - > don't,don't,don't,don't,don't,don't,don't,don't!!!! Yup, that's my experience as well. DagT
