Search the Community
Showing results for tags 'vbuc'.
Oracle Data provider (ODP.Net) in a migrated project Old Visual Basic 6 applications interacting with Oracle databases may rely on the MSDAORA driver in the connection string to establish such communication when that code is converted to .NET, the Visual Basic Upgrade Companion (VBUC) will keep the same connection string and therefore be use the old MSDAORA driver. But, in .NET we can take advantage of the Oracle Data Provider (ODP.Net) technology developed by Oracle instead. The following VB6 code shows a database connection though the MSDAORA provider: Dim oConn As ADODB.Conn
Upgrade from TDBG 6 to TDBG 7 Summary The Visual Basic Upgrade Companion supports TrueDBGrid 7.0 and later versions, but not TrueDBGrid version 6.0. To migrate code containing version 6 controls, you must first upgrade TDBG 6.0 to TDBG 7.0 Problem Description TrueDBGrid 6.0 defines some properties of the grid in the frx file, while TrueDBGrid 7.0 defines them in the frm file. When a project in Visual Basic has a form, which contains a grid of type True DB Grid 6.0, some characteristics, such as properties of columns, positions, and more are defined in the
This is converted code from a project. It is a basic combo box loading routine. The cbo.RowSource is an MSDATASRC an the rst is the created / converted ADORecordSetHelper. They aren't compatible! Okay so what can I assign in code to make this work?
Even if you don't have a license for the VBUC you can still use it to analyze your VB6 application. This analysis will provide you with some information about your project(s) like number of lines of code (LOC), design lines, components, and more. Launch the VBUC and point to a folder containing a *.vbp file (valid VB6 project). Then go to the Tools menu and click Assessment: Click run, and the assessment will process all the files it finds. If you get an "unresolved references" warning, you can click the "Resolve References" button on the left and resolve those references (righ