The rule of 72 is used to make a quick estimate of the time required for prices to double due to inflation. If the inflation rate is r percent, the the Rule of 72 estimates the price will double in 72/r years. For instance, at an inflation rate of 6 percent, prices double in about 72/6 or 12 years. Write a program to test the accuracy of this rule. The program shoule display a table showing, for each value of r from 1 to 20, the rounded value of 72/r, and the actual number of years required for the prices to double at an r percent inflation rate.(Assume prices increase at the end of each year.) Assignment Requirements: Rule of 72 calculation is correct Actual calculation is correct (hint – use a loop!) Function used for the actual calculation Data is shown in the format outlined in the book – loop is used to produce the table. My calculate method is where i am having trouble. I dont know what to do to get the actual amount of years that it takes to double in price.

I already have the RuleOf72 figured. • → *new* Get practical advice and learn best practices for moving your applications from RDBMS to the Couchbase Engagement Database. (sponsored) • → Learn to shorten database dev cycles, integrate code quality reviews into Continuous Integration workflow, and deliver code 40% faster. (sponsored) • → See a demo showing how you can build a globally distributed, planet-scale apps in minutes with Azure Cosmos DB. (sponsored webinar) • → A complete overview of Cloud Computing focused on what you need to know, from selecting a platform to choosing a cloud vendor. • → Better understand the signs that your business has outgrown its current database.

(sponsored webinar). Click Here to Expand Forum to Full Width Survey posted by VBForums.

This is an extract of information provided by Microsoft to those that has already bought Visual Basic 4.0. It's kinda useless when you already have it, so read it before you buy it. Author: Will the 16-bit and 32-bit versions of Visual Basic 4.0 run on Windows 95? The 16-bit version of Visual Basic for Windows version 4.0 will run on Windows, Windows for Workgroups, Windows NT, and Windows 95. Under Windows NT and Windows 95, it is handled as any other 16-bit application.

Project path: src Compilers VisualBasic Test CommandLine BasicCommandLineTest.vbproj. Lines of code: 10,103. Bytes: 513,872. Declared symbols: 347. Declared types: 17. Public types: 5. Indexed on: November 17. File: CommandLineTests.vb Web Access.

The 32-bit version will run only on Windows 95 and Windows NT version 3.51 or greater. On Windows NT, your application will run in a 16-bit environment provided by the Windows On Windows (WOW) layer, which allows Windows NT to run 16-bit applications in a protected environment. Can I load a VBX control in the 32-bit version of Visual Basic? VBX custom controls are limited to 16-bit and are fully supported only by Visual Basic 3.0 and the 16-bit version of Visual Basic 4.0.

Visual Basic 4.0 uses the new OLE control model as its main control architecture. Visual Basic has moved to this new, open control model to support controls in both 16- and 32-bit environments. The OLE Control architecture merges all of the benefits of the VBX custom control with OLE. The new OLE Controls can be used in any OLE client application and are available on 16-bit as well as 32-bit platforms. Visual Basic 4.0 includes OLE controls (.OCX) that are upgrades to the VBX custom controls that shipped in previous versions.

Automatic conversion is provided to replace the VBX references in projects with references to OLE controls. Visual Basic 4.0 will ship with OLE equivalents of all of the controls shipped in Visual Basic 3.0, in addition to several brand new OLE controls in both 16- and 32-bit versions. Visual Basic will continue to support VBXs in the 16-bit version only.

How can I write an application for 16-bit and 32-bit systems at the same time? Microsoft has taken a number of steps to assure source code compatibility between 16-bit and 32-bit applications: • All Visual Basic-provided language is portable. • All custom controls in the product have identical object models. • Basic file I/O enables files to be shared by applications running on different platforms.

Visual Basic 4.0, Professional and Enterprise Editions include both 16-bit and 32-bit versions of VB.EXE. Using a single source code tree, you can create 16-bit applications that run on Microsoft Windows 3.X, 32-bit applications that run on Microsoft Windows NT 3.X (Intel), and 32-bit Windows 95-based applications. By taking advantage of the new conditional compilation switches in Visual Basic 4.0, you can quickly recompile the same source code to target and exploit the capabilities of different Windows platforms. Conditional compilation switches allow you to easily target different platforms or languages using a single source code tree and a simple recompile. Visual Basic provides both the language and command-line support for conditionally compiling declarations and procedural code into an application. Both the Project Options dialog and the Visual Basic 4.0 command line allow the setting of constants that are subsequently used in evaluating #If.#Else.#End If structures. #If Win16 Then' Use Win16 calls.

Declare Function GetWindow Lib 'User' (ByVal hWnd As _ Integer, ByVal wCmd As Integer) As Integer #Const ANSI=True #Else ' Use Win32 calls. Declare Function GetWindow Lib 'User32' (ByVal hWnd As _ Long, ByVal wCmd As Integer) As Long #Const ANSI=False4 #End If Can a Visual Basic 4.0 32-bit application run on Win32s? Win32s is a subsystem of DLLs which extends the Windows 3.1 16-bit operating system by translating 32-bit calls to the underlying 16-bit operating system. Programs written with the 32-bit version of Visual Basic running on Windows 3.1 with Win32s would generally run slower (due to the extra memory and overhead of the translation layer) than the same program created with the 16-bit version of Visual Basic. Instead of using the more limited Win32s features, Microsoft chose to have the 32-bit version exploit the more advanced 32-bit features available only on Windows 95 and Windows NT. Can a developer create DLL files with Visual Basic 4.0? Visual Basic version 4.0 includes an option to make OLE DLL files.

These files behave similarly to standard DLLs except that they use OLE as an interface to the objects described by the DLL. With Visual Basic 4.0, you can create reusable business objects that can be shared across applications. Rather than having to create DLLs using a C compiler or other language, you can now easily create reusable objects entirely from within Visual Basic. These OLE components accomplish the reusability of DLLs and are easier to reuse because they are essentially self-documenting.

At design time you can browse the components with the Object Browser and examine what methods and properties the OLE objects expose. Similar to the way in which VBX vendors encapsulated their expertise into controls, Visual Basic programmers can now rapidly package their business rules, commonly used code libraries, as well as any legacy code into reusable, programmable objects. Once created, these libraries of reusable objects, complete with custom properties and methods, can be used by any application capable that supports OLE Automation. A few examples of applications that can reuse these objects are Visual Basic 4.0 (which can both use and create OLE objects), Microsoft Excel 5.0, Microsoft Access 2.0, and Microsoft Project. Future versions of Microsoft SQL Server, Microsoft FoxPro, Microsoft Word For Windows, and Windows will also take advantage of these objects. Does this mean that I can use a Visual Basic created DLL from other languages? Yes, you can use the OLE DLLs from other languages (such as Microsoft Visual C++), but you do not declare the functions in the DLL like you would a Windows DLL function.

Instead you access the functions via the OLE interface. Will Visual Basic 4.0 exist for MS-DOS and Macintosh platforms? Visual Basic 4.0 incorporates the portable Visual Basic, Applications Edition language engine.

Microsoft Excel 5.0 was recently released for the Macintosh and along with it the Visual Basic for applications component of Microsoft Excel, so the language engine is there. There are no commitments at this time for a version of Visual Basic for the Macintosh or for MS-DOS, but consideration is one based strictly on a good business case. Plant Tycoon Torrent Crack more. Does a specific version of 32-bit Visual Basic exist for Windows NT on MIPS, ALPHA, PPC, platforms? Preliminary discussions have occurred concerning all other major architectures that support Windows NT, and although no commitments have been made, this is certainly a possibility for the future. The 16-bit version of Visual Basic 4.0 will run on any machine which can run Windows NT. Windows NT includes a Windows On Windows (WOW) emulation layer which can run 16-bit applications.

Does the 32-bit version of Visual Basic provide statements and functions for multitasking? Currently Visual Basic 4.0 does not support threads on Windows NT 3.5 or Windows 95. Research indicates that the main reasons Visual Basic programmers would want to use threads in a Visual Basic application would be for asynchronous database queries, printing, or file I/O operations. Microsoft is expecting providers of data sourcing OLE controls to provide the former, and will consider the latter for future versions. Does Visual Basic 4.0 use the new controls of Windows 95? Visual Basic does use the new Windows 95 controls, but because these are 32-bit controls for a 32-bit operating system, they are only available in the 32-bit version of Visual Basic.

Do you know if the third party vendors will be selling OLE Controls soon? There a large number of control developers who are migrating existing VBX controls to the OLE control model as well as those who are writing new controls.

There should be a large number of controls available immediately after Visual Basic releases. Do I need to change my Visual Basic 3.0 applications to compile with the 32-bit version of Visual Basic 4.0? There are two significant changes that need to be addressed to re-compile a Visual Basic 3.0 application to Visual Basic 4.0 32-bit. First, if API calls are being used by the application, you must change your API calls to the appropriate target environment. Win16 and Win32 provide APIs with similar functions but different Declare statements (to take into account the size of the data types). Visual Basic 3.0 typically uses the 16-bit declarations.

The 32-bit version of Visual Basic 4.0 must use the 32-bit API declarations. Rather than simply replacing the existing API calls, you can use Visual Basic 4.0's conditional compilation feature to target both 16- and 32-bit platforms from a single source code tree. Second, the 32-bit version of Visual Basic 4.0 makes use of the newer OLE Control architecture exclusively. VBXs are not supported for the 32-bit version. This is not a problem for VBX controls shipped with previous versions of Visual Basic. All of these controls have OLE Control counterparts (in Visual Basic 4.0, these files all end in.OCX). You will be prompted to upgrade these controls the first time you load your project into Visual Basic 4.0.

However, you will need to acquire OLE Control upgrades to any third-party controls used in your applications. While Microsoft has made the technology available for control developers to easily port their existing VBX controls to the new OLE Control technology, there is no guarantee that all of the available VBX controls will be available as OLE Controls. Contact the control vendor for upgrade information.

The 'Basic Language' code of both the 16-bit and 32-bit versions of Visual Basic are fully compatible. Creating a 32-bit application that runs on either Windows NT 3.5 or Windows 95 from a Visual Basic 3.0 (or 16-Bit Visual Basic 4.0) application is a simple matter of loading an existing 16-bit Visual Basic application into the 32-bit version of Visual Basic and choosing the Make EXE File command from the File menu. Do I need to change my Visual Basic 3.0 application to compile with the 16-bit version of Visual Basic? To run a Visual Basic 3.0 application with the 16-bit version of Visual Basic, load the source code into the 16-bit version of Visual Basic 4.0 running under Microsoft Windows 3.x, Microsoft Windows 3.x, Windows NT 3.51, or Windows 95, and make an.EXE file. Does Visual Basic 4.0 support DBCS? All versions of Visual Basic 4.0 are Double-Byte Character Set (DBCS) enabled, in that all dialogs accept DBCS characters, all edit controls can accept DBCS text, and strings specified in code can contain DBCS characters.

In what languages is Visual Basic 4.0 available? Visual Basic for Windows version 4.0 is slated for release in French, German, Italian, Spanish, Chinese, and Japanese. What is the difference between Standard and Professional versions?