This will work, although I'm sure there are many more elegant solutions:
Public Function NewCode() as long
dim intFileNo as integer
dim lngCode as long
intFileNo = freefile
open app.path & "\CodeNoFile.DAT" for random as #intFileNo len = 4
if LOF(intFileNo) = 0...
You have the VB5 version of the Package and Deployment Wizard if you have the Pro or Enterprise edition. Go to AddIns menu and select Add In Manager (this might be on Tools menu in VB5?) Anyway, there you can select PDW to be added to the Add Ins menu. Then you can select it and run it and it...
Take the parenthesis off the name of the control in your call to the sub. I.e., ApiCalls.SaveControl chkSimulate instead of ApiCalls.SaveControl (chkSimulate)
The Working Model of VB does not have the compile feature nor does it include the PDW (PAckage & Deployment Wizard). If you want to have these you must buy the Professional or Enterprise edition. The Working Model is basically for students of VB to use and cannot be used in a production...
RE: misspelling variables. As long as you always "Require Variable Declarations" by including Option Explicit in the Gen Declarations section of every module, misspelling variable names becomes a very minor problem. Each one is flagged as a compile error as soon as it's encountered...
I have a VB6 app that has evolved over a year or so, during which time I installed SP4. My app includes a couple of small Access databases connected to it via the Data Control. My problem is it now requires a number of .dll files in the deployment package that appear to be just updated versions...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.