I have noticed that even those who assert that everything is predestined and that we can change nothing about it still look both ways before they cross the street.
A sort of generic question for you. I have worked may way through these lessons and put what I have learned to good use in my Ambulance Service database. I just bought and went through your seminar on relationships and learned much more. I am anticpating taking the SQL seminar and was wondering if knowing SQL would replace the need to use datasets or is there a need to use both disciplines? Are recordsets a precurser to using SQL?
Reply from Richard Rost:
They compliment each other pretty well. You can learn one or both and use each of them quite well together, in fact.
If anything, I should have made a comprehensive SQL series BEFORE recordsets. I personally think that recordsets are MUCH more powerful than SQL, however SQL is good for short, quick operations (like quickly deleting, adding, or editing some records). And so many things in Access are based on SQL (listboxes, combo boxes, subforms, etc.) that it really helps to fully understand how the SQL language works.
HOWEEVER that being said, if you have anything COMPLEX to do, recordsets are the way to go. A lot of what I taught in AC320-329 probably COULD have been done with SQL, but it was necessary to show you simple recordsets in order to build up to more complex ones.
Learning both will make you a very well-rounded developer... and I'm not just saying that so you buy more lessons. However, if I had to pick one over the other, I'd probably go with recordsets myself. I use them a lot more often.
Sorry, only students may add comments.
Click here for more
information on how you can set up an account.
If you are a Visitor, go ahead and post your reply as a
new comment, and we'll move it here for you
once it's approved. Be sure to use the same name and email address.
This thread is now CLOSED. If you wish to comment, start a NEW discussion in
Microsoft Access 328.