Ye' old general discussion board. Basically, for everything that isn't covered elsewhere. Come here to shoot the breeze, shoot your mouth off, or whatever suits your fancy. This forum is not for asking programming related questions.
Using a RDBMS would likely improve performance if you use JOINS and insert and delete records quite often, if you are usually just reading a bunch of data from one table at the time and adding now and again a flatfile system is fine (Access would sort of be one of those although Jet provides an SQL api).
NEVER use SELECT * , ALWAYS use explicit columns..
Because of that MySQL has the LIMIT function, a lot of peopla are abusing this and make a lot of unecessary resource using queries, I am not sure if TOP is widely supported, rarely used or seen that myself.. To me, the proper way of chunking/paginating is to first query for the id's (SELECT id FROM bla bla), all of them, then based on this paginate and fetch the wanted records with a WHERE asking just for the id's you are interrested in, and cache this id list for the next page/fetch so that you dont have to do that query again...
Unless ofcourse you are talking millions of records, then you want to limit on other things like dates or location etc for the initial query
i don’t see any drawbacks using LIMIT in mysql, in fact it lightens the task since i just need a single query. i usually use SELECT * if i need all the fields in the recordset so in one way it’s a help.
what i want to know is if there is an equivalent of mysql SELECT LIMIT in access/jet.
I dont know Bill gates stuff wekk enough to know that..
It may be good (enough) for your application and envrionment, but from a developers point of view you want to do what you can for versatility, re-usability and effectiveness without extensive cost increase, so using SELECT * and LIMIT is cheap-cheats that may cost later..