VBS is useful for scripting/automating tasks you perform on a repetitive basis. For instance, when a user's account is locked out of the network, I can click a script, enter the user's login at the prompt and their account is unlocked. No wasted trip to the server. We have a few applications that upon entry you have to enter a login/password and pass thru a few other prompts (clicking OK,yes,etc..) - I have those scripted so with the click of my script, I'm in the application.
VB (not .NET) itself is not what I would consider feature-rich due to it's heavy dependance on COM and ActiveX. However, there are a plethra of examples available and the language itself is relatively easy to pickup and maintain.
VFP is an OOP data-centric language. It has a native data format. The language itself is quite robust, the string handling functions are exceptionally fast, and the list goes on and on.
Choosing between VFP and VB typically comes down to which you are more comfortable with. Jon Hawkins
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.