My vba coding I would say in intermediate however there are times when some things you just need other peoples examples to get yourself going which you can edit and tailor to your needs.
One thing I have noticed is I have been switching between a couple of dao / ado references in my vba, in different modules etc but still I have been using both. Now my knowledge of both is limited but I know they both have their unique advantages.
My question is simple, would the database be affected in any way by switching between the two? From looking at:
http://msdn.microsoft. com/en-us/library/aa164825(office .10).aspx
It seems like ado is the way forward if I wish to be upgrading to sql server later on but I have no clue on the size of the task to switch from DAO over to ADO, I'm assuming it is quite pain free once you get used to terminology/syntax stuff, but I could be totally wrong.
Im using Access 2003 at the moment and no major system upgrades in the near future.
One thing I have noticed is I have been switching between a couple of dao / ado references in my vba, in different modules etc but still I have been using both. Now my knowledge of both is limited but I know they both have their unique advantages.
My question is simple, would the database be affected in any way by switching between the two? From looking at:
http://msdn.microsoft. com/en-us/library/aa164825(office .10).aspx
It seems like ado is the way forward if I wish to be upgrading to sql server later on but I have no clue on the size of the task to switch from DAO over to ADO, I'm assuming it is quite pain free once you get used to terminology/syntax stuff, but I could be totally wrong.
Im using Access 2003 at the moment and no major system upgrades in the near future.
Comment