Hi randem:
I don't Know if you can help me but i had installed an apllication that a lot of users are installed in Windows Vista but in this computer he APP don't work because something in the database..
The error when the APP start is :
RUntime error 91 - Object or with Block variable not set
My script for this APP is:
; InnoScript Version 10.3 Build 3
; Randem Systems, Inc.
; Copyright (c) 2002 - 2010, Randem Systems, Inc.
; Websit..\..\.. https://randemsystems.com (https://randemsystems.com)
; Support: https://randemsystems.support (https://randemsystems.support)
; OS: Windows XP 5.1 build 2600 (Service Pack 3)
; Derived from VB VBP Project File
; Designed for Inno Setup Version: 5.2.3
; Installed Inno Setup Version: 5.2.3
; Local Machine Settings. Use these settings as a template for your installation folders
; {app} : C:\Program Files\Randem Systems\innoscript
; {appdata} : C:\Documents and Settings\Manuel Sacramento\Application Data\Randem Systems\innoscript\
; {localappdata} : C:\Documents and Settings\Manuel Sacramento\Local Settings\Application Data\Randem Systems\innoscript\
; {cf} : C:\Program Files\Common Files\Randem Systems
; {tmp} : C:\Documents and Settings\Manuel Sacramento\Local Settings\Temp\
; {commonappdata} : C:\Documents and Settings\All Users\Application Data\Randem Systems\innoscript\Release\
; {pf} : C:\Program Files\
; Dat..\..\.. Agosto 09, 2010
; VB Runtime Files Folder: C:\Program Files\Randem Systems\InnoScript\InnoScript 9\VB 6 Redist Files\
; Visual Basic Project File (.vbp): ..\..\..\Projectos VB\GIA - GEST
Hi sacremento,
The one thing that jums out to me is I do not see any database being deployed. Where is you database located? Hopefully you do not have ANY hard coding in your application as to where anything is located for this could be an issue installing on a 64 bit system as to the location of \Program Files\ being redirected to \Program Files (x86)\ and other virtualizations such as registry entries.
Is the computer where you are getting this error on a 64 bit version of Vista?
Also runtime error 91 is usually caused by a With, do, while or object error in code (unhandled exceptions). It could be hard to trace on someone Else's computer unless they will agree to testing. If so you can use VB Source Trace (https://randemsystems.com) to locate where the error resides.
Hi Randem:
In fact, just because the problems of the windows Vista i create the database trought code.
When the APP starts the DB is created!
In fact the windows is 64 bits
Are you hard coding anything? that will put things where you do not expect them to be.
I had review all code and i don't see why this happen...I had installed in others PC's with Vista 32 and 64 and the APP work...
It's very strange!
Are you creating object via code? IE. CreateObject
Object!!!...What kind of object do you refere?
I had know in the last minute that windows the user use is Vista Ultimate 64 bits
Do you use CreateObject in your code anywhere?
Ah ok...i see what you mean...No i don't use
Have you modified the script?
I see two lines:
Source: c:windowssystem32mscomct2.ocx; DestDir: {sys}; Flags: regserver restartreplace sharedfile;
and two references:
; Crystal Reports ActiveX Designer Run Time Library 11.5 - (craxdrt.dll)
Otherwise the script looks fine
One way you can track down where in your code this is happening is to use VB Source Trace to add routine tracing to your code so that when you run the exe on the target machine it will give you a log of where the error happened in your application. The you put line numbers in that routine with an error routine that tells you on which line the error was generated. Then you will have a clue to what actually caused the issue and it should be fairly clear what to do to remedy the situation.
OK..i go try that and see what line is the error
Thanks
Report back on what you find...
Hi Randem:
I had find the problem...Well for this case the problem it was the MDC_Jet that i had use in my script...I don't had incorporate the last version that support Vista and Seven..
I had create a new script installed and now everything work fine..
Thanks for your help
OK, I completely overlooked the older Auto OS Updater that you had in your script because the current InnoScript (since 10.2 build 10) will not place that version of the Auto OS Updater in your script because of the update.