>I will definitely agree with you on your last section. VB seems to have better handling and control of most external libraries outthere, but, is this really so? Shouldn't VFP do (supposedly) the same?. Are people happy with just performance and not speed and interface?
>
>Probably Gates & Co. should think about building VB as a function library for VFP 7.0 (Hey, there goes my wish list for VFP 7!!)
>
Take a look at SCROBJ.DLL - reality is gonna bite you long and hard before VFP7 ever hits. You can code in VBScript and use it inside of VFP
NOW. The following is excerpted from the MSDN:
Packaging Script as Objects
Windows® Script Components provide you with an easy way to create powerful, reusable COM components using script. You create script components using any scripting language that supports the Microsoft® active scripting interfaces. Script languages that support these interfaces include JScript®, Visual Basic® Scripting Edition (VBScript), PerlScript, PScript, and Python.
Note For more information about active scripting interfaces, see the Microsoft Scripting Web set at
http://msdn.microsoft.com/scripting/.
Script components:
Allow you to create COM components using script.
Provide you with access to a broad range of system services.
Are easy to create, maintain, and deploy.
Are small and efficient.
Using script components, you can create COM components for a variety of tasks, such as performing middle-tier business logic, accessing and manipulating data, adding transaction processing to applications, and adding interactive effects to a Web page using DHTML Behaviors.
You can use script components in any host application that supports COM. For example, you can create a script component and then use it as a COM component from an application written in Microsoft Visual Basic or in Microsoft Internet Explorer.
Certain types of script components are written to interact with specific environments. For example, you can create a Behavior script component that implements DHTML Behaviors for Internet Explorer 5.0. In that case, the host application must be Internet Explorer 5.0. Similarly, an ASP script component runs in a Microsoft Internet Information Services (IIS) server environment.
How Script Components Work
A script component acts like other COM components: it exposes properties and methods and can fire events. You instantiate a script component from a host application such as a Visual Basic program or a Web page. You can then get or set its properties, call its methods, and respond to events that it fires, just as you would for any COM component. Creating a COM component as a script component, however, is a little different from doing so in other environments.
Sample Script Component File
As the script component author, you create a script component file (.sct file) that contains XML elements. The file resembles an HTML file — some of the tag names are the same — but does not include elements to lay out text. In addition, because a script component is an XML file, it is parsed more carefully than an HTML file, and therefore has to conform more closely to XML conventions. For details, seeScript Component Files and XML Conformance.
