Q102030: Microsoft Systems Journal: September 1993
Article: Q102030
Product(s): Miscrosoft Systems Journal
Version(s): for September 1993
Operating System(s):
Keyword(s):
Last Modified: 19-MAY-2000
-------------------------------------------------------------------------------
The information in this article applies to:
- Microsoft Systems Journal (MSJ) for September 1993
-------------------------------------------------------------------------------
SUMMARY
=======
NOTE: "Microsoft Systems Journal" does not make any representation or warranty,
expressed or implied, with respect to any code or other information herein.
"Microsoft Systems Journal" disclaims any liability whatsoever for any use of
such code or other information.
This article lists the filenames and Snumbers for files available from online
services that contain the source code described in articles published in the
September 1993 issue of the "Microsoft Systems Journal."
FILES AVAILABLE FROM ONLINE SERVICES
------------------------------------
Item ID Filename Description
------- -------- -----------
S14212 VB3.EXE The VB3.EXE and VBDIST.EXE files contain the
S14213 VBDIST.EXE source code for the article named "Harnessing the
Database Access and OLE Support Capabilities of
Visual Basic 3.0," by Joshua Trupin.
Visual Basic version 3.0 ships with the Microsoft
Access 1.1 Engine fully integrated into the
language plus full OLE 2.0 container function-
ality. It will allow developers adding data access
and OLE 2.0 support to their apps to slice weeks
off their development cycle.
S14210 BEASTIES.EXE The BEASTIES.EXE file contains the source code for
the article named "Slay the Porting Beasties:
Dave's Top Ten Tips for Migrating to Windows NT,"
by Dave Edson.
Porting your 16-bit Windows-based applications to
Windows NT is relatively easy, once you get advice
from a veteran who knows where the evil lurks.
Dave Edson shares some less-than-obvious porting
tips he had to figure out the hard way.
S14211 OLE2.EXE The OLE2.EXE file contains the source code for the
article named "OLE 2.0, Part II: Implementing a
Simple Windows Object Using Either C or C++,"
by Kraig Brockschmidt.
OLE 2.0 and its object model don't solve every-
thing, but they should make it easier for you to
express object-oriented ideas under Windows. Here,
Kraig Brockschmidt discusses various types of
Windows Objects, how to get a pointer to one, and
the interfaces they support.
INSTRUCTIONS FOR DOWNLOADING
----------------------------
You can download any of these self-extracting files from the following services:
- Microsoft's World Wide Web Site on the Internet
On the http://www.microsoft.com home page, click the Support icon.
Click Knowledge Base, and select the product.
Enter kbfile <FILENAME>.EXE, and click GO!
Open the article, and click the button to download the file.
- Internet (anonymous FTP)
ftp ftp.microsoft.com
Change to the Softlib/Mslfiles directory.
Get <FILENAME>.EXE
- The Microsoft Network
On the Edit menu, click Go To, and then click Other Location.
Type "mssupport" (without the quotation marks).
Double-click the MS Software Library icon.
Find the appropriate product area.
Download <FILENAME>.EXE.
- Microsoft Download Service (MSDL)
Dial (425) 936-6735 to connect to MSDL
Download <Filename>.exe
For additional information about downloading, please see the following article in
the Microsoft Knowledge Base:
Q119591 How to Obtain Microsoft Support Files from Online Services
Additional query words: 3.10 msj sep
======================================================================
Keywords :
Technology : kbMSJSearch
Version : :for September 1993
=============================================================================
THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.
Copyright Microsoft Corporation 1986-2002.