VB/DAO vs Access/VBScript?

[Mark]

I am a novice with Access, and it appears to me that I will
need to write a fair amount of VBscript to do anything
complex. And since I will be writing VB code, I am
wondering what benefits Access development offers vs
VB/DAO development.

Can anyone here point me to a good side-by-side
comparison?

Thanks
-Mark

[teddysnips]

Mark wrote:

I am a novice with Access, and it appears to me that I will
need to write a fair amount of VBscript to do anything
complex. Highly unlikely. Access' native programming language is VBA.
And since I will be writing VB code, I am
wondering what benefits Access development offers vs
VB/DAO development.

Well, you get the whole shooting match under one roof, so to speak.
Furthermore, compared to VB and its reliance on Crystal Reports (makes
sign of the cross), Access with its tremendous report building
capability is the business.

I have extensive experience with Access, a little with VB, and quite a
bit with VB.NET. If I can do it in Access, I will.

Edward

[Steve Jorgensen]

On Thu, 19 May 2005 19:06:42 -0700, "Mark" <no****@thanksanyway.org> wrote:

I am a novice with Access, and it appears to me that I will
need to write a fair amount of VBscript to do anything
complex. And since I will be writing VB code, I am
wondering what benefits Access development offers vs
VB/DAO development.

Can anyone here point me to a good side-by-side
comparison?

Actually, Access uses VBA not VBScript. VBA is really the same language as VB
minus the ability to create a stand-alone executable and minus a few other
trivial things like the ability to easily create custom iterators.

That's very different from VBScript that has no variable types except variant
and no error trapping, etc.

[Mark]

<te********@hotmail.com> wrote:

Mark wrote:

I am a novice with Access, and it appears to me that I will
need to write a fair amount of VBscript to do anything
complex.

Highly unlikely. Access' native programming language is VBA.

Oops, my bad. Yes, I meant VBA.