 |
 |
 |
 |
 |
VB RezQ

Support for VB RezQ

|
 |

This page provides additional information about VB RezQ.
Please read this section carefully before contacting us regarding
problems.
Some frequently asked questions about VB RezQ are answered
here.
The operation of VB RezQ relies on an understanding of the
internal format of compiled Visual Basic executable files. There is no
publicly available definition of this format. A tedious process of
compiling test programs and inspecting the result has allowed much
of it to be deduced. It is unlikely, however, that this testing has
covered every possible aspect and it is to be expected that the
occasional executable will cause problems for VB RezQ.
Error and Warning Messages
This page details the error and warning
messages that may be produced by VB RezQ and gives guidance on what
action you should take.
Version History
The current version of VB RezQ is v3.3a.
V3.3a increases full recovery of the properties and events for controls to 27 commonly used
custom controls with the addition of support for this control:-
TabbedDialog (TABCTL32.OCX),
V3.3a also corrects the recovery of long/complex string properties in embedded instances of
UserControls; corrects the occassional corruption of recovered subroutine names; and adds
trapping of any attempt to open a file with an Unicode filename which would lead to a runtime error 52.
Information on previous versions of VB RezQ is available here.
Updates
Registered users can request a free upgrade to the current version
by sending an e-mail to
VB RezQ Support (see below).
Contacting VB RezQ Support
For any questions about buying VB RezQ please see our
FAQ.
If you have problems with buying VB RezQ please contact
RegNow Customer Service
and not VB RezQ Support.
Registered users can contact us for technical support by e-mail to
support@vbrezq.com.
Please provide as much information as possible to help us improve
VB RezQ.
Those who are not yet registered users are asked to study our
overview,
example and
FAQ and try our
demo version before sending questions
to our support desk.
|
|
|
|