Vb/vba?

[hi there]

i know similar questions like this have been asked numerous times and i apoligize if this seems repetitive. i've read through the other posts but i'm still looking for an answer. he goes:

1. VB has come up at work lately and was wondering just how different VB is from VBA. folks at my work have been asking a lot of questions about developing larger client/server type applications. that has led me to do some research on SQL server applications. i've read people recommending using SQL server with a VB front end so naturally i'm wondering how involved is it in developing this VB front end as opposed to an Access front end?

2. can i use what little VBA knowledge i have to work with VB?

3. furthermore, do y'all see any advantage to using a VB front end as opposed to an Access front end?

4. and lastly has anyone had any experience with a book titled "VB and VBA in a Nutshell." i kinda looking for a book that compares the 2 languages and notes the differences.

as always i am extemely grateful to any and all responses to my questions. many thanks.

 

[llkhoutx]

VBA is a subset of VB and and to me is more user friendly that VB. I'm sure someone will post a more technical answer to your question.

As I recall, "VB and VBA in a Nutshell" just addresses the instruction set as opposed to how to use it. If that's what you're looking for OK.

 

[hi there]

thanks for the responses pat and llkhoutx. they were very helpful. i understand that VBA comes in many different flavors (Access, Excel, PowerPoint, Outlook,...etc) and syntax will vary based on the applications object hiearchy and application functions. does anyone have any opinion about the question of using Access as the front end for a client/server application as opposed to VB. based on your reponse pat it seems like VB is a much more robust language capable of doing much more (e.g. interacting with other applications) than VBA. however it also seems like i'm going to have a learning curve. so do you think the benefits outweigh the costs?

thanks everyone

 

[hi there]

hi pat. thanks for all the information. as always your responses are very helpful. i've read several of your posts where you describe using Access as a front end to more powerful applications like Oracle. i think this is probably the way for me to go, but i'm still confused about how i would incorporate a client/server application using individual Access front ends. in these instances are you using the MSDE? will using Access as a FE prevent me from harnessing the power of the "true" client/server applications like SQL Server, Oracle,...? would this be an implementation/maintenance nightmare over a large corporate network? i've just completed a small application for a facility's local network where i split the dbase into FE/BE (both Access) and placed copies of FE on each users desktop, but it does get a little slow when 7 or so users are updating records. it can also be somewhat of a nightmare when i have to make changes to the dbase and re-destribute it. i've read some posts on the forum and writing batch files to help with this, but i need to do some more research before attempting this. thanks again for all your comments.

 

[hi there]

thanks pat. i've read one of your posts where you describe this method of placing a timestamp table in the FE and BE and notifying the user when an update is necessary. it looks like i've got a lot more studying to do before i attempt such an application, but thank you again for all of your responses. now i have a better idea of what direction i should pursue.

many thanks