SQLWindows 5.0.3 minimized deploy catalog

SQLWindows Deploy

8/1/97

This paper submitted by Carsten Barner Nielsen of ISS Data A/S, comments from David Burke of Centura Software Corporation, and edited by Charles McLouth of Centura Software Corporation.

This document is intended to answer the FAQ for deployment requirements of SQLWindows 5.0.3, ReportWindows 3.0.3 and Quest 3.0.3 on a Windows 3.x environment.

Minimum Requirements

SQLWindows

NOTE: If you use QuickObjects you'll need the support .DLL's that QCKDVC.APL will load too.

NOTE: If you use Visual toolchest add: VT50.DLL

ReportWindows(Design Mode)

In addition to the SQLWindows required:

Quest

In addition to ReportWindows required:

NOTE: When installing QUEST without using the official install sets, you might want to read some notes from the Centura file QUEST.WRI:

----------------8<---------------------snip----------------8<----------------snap------------------------

Tool bar does not display activity icons when you first start Quest

This error could be caused by one of the following problems:

• The questdir keyword is missing in the Quest section of the WIN.INI file or is pointing to the wrong directory. In a default installation, questdir should be set up as:

[Quest]

questdir=C:\GUPTA

• Some activity entry is missing under the Quest section in the QUEST.INI file:

[Quest]

Activity1=Form30.dll

Activity2=Query30.dll

Activity3=Report30.dll

Activity4=SQL30.dll

Activity5=Catlog30.dll

Activity6=Data30.dll

Activity7=Graph30.dll

----------------8<---------------------snip----------------8<----------------snap------------------------

Connectivity to SQLBase

Please refer to File requirements for deploying a SQLBase engine at http://www.centurasoft.com/support/tech_info/knowledge_base/sbsinfo/fileli~1.html

NOTE: 'Rule of thumb' - use the ones from your CLIENT COMPONENTS disk.

NOTE: For dbwservr.exe add START.DBS if you ever intend to create a .DBS

HINT:

I always store the backend components separately in the C:\SB.xxx, where xxx is the version number of the backend, then using PATH and SET SQLBASE=C:\SB.xxx, things run perfect and upgrading to a new version off the backend is easy...

Using this method, and keeping the backend-related files a seperate sets in each directory, I manage both SQLBase 5.x and SQLBase 6.x on the same computer with succes. In each SQL.INI that you have, be sure that the dbdir= is pointing correct.

I also (re)move any backend component that I find floating around, ie. installed by SQLWindows, QUEST, SQLConsole ao.

WINDOWS SYSTEM:

While making install sets I have found that this files should be in windows\system:

• odbc.dll - (if you use ODBC)
• ctl3dv2.dll

(there is of course many other files in this directory....)

SQLWindows 5.03 introduced that this files also should be in windows\system:

• ole2.dll
• compobj.dll
• mfcoleui.dll
• storage.dll

NOTE: Only install components into your users windows system catalog if your users do *not*, have them in advance.

INSTALLATION DISK's:

Having isolated the needed components, you are ready to make better, smaller and faster installation utilities, using you favorite install wizard. To keep the size off the installation disks even smaller, you can, if it is a first time installation at your users, distribute a .SQL file for creating the database instead off distributing the .DBS. SBCAPI.ZIP (load-utility) from LIB 7 is a good candidate for doing this, as it can be submitted using command line parameters.

When you deploy, do not forget your own beautiful .EXE,.QRP's,.INI etc. etc. :)).

NOTE:

Running on a 'minimized' deploy environment, it is very likely you one day will have a referance to a .DLL that is not present at your users computer when you update to a new version of your .APP. It is very important test your own 'minimized' deploy environment, before you distribute. When you have done, test it again !!!

For debugging use WINAPPS.EXE, SQLEDIT.EXE and trial and error.

And do *not* delete the original deploy catalog, you might need it one day !!!, make your own.

MY RECOMMENDATION

The recommendations that I give in this contribution are my own, they are *not* Centura Software Corporation's official advice. The official policy is that all, and only, the files in the DEPLOY folder should be distributed together with your .app & qrp's.

This are the comments from Centura Software Corporation:

Unless you've negotiated an OEM deal with your local Gupta/Centura rep, you are not allowed to deploy Quest, ReportWindows design time and SQLBase files. When you purchase our product, the license allows you to distribute SQLWindows (or CTD) deployment files only (plus your generated application files: .exe, .apd). [At least that's the case in North America, I can't say I'm 100% on this elsewhere.]

About the Author

Carsten Barner Nielsen from ISS Data A/S of Compenhagen is a TeamAssist on Compuserve he can be reached via e-mail at 101463.2173@compuserve.com.

David Burke of Centura Software Corporation has commented on the deploy policy.

Edited by Charles Mclouth, Centura Software Corporation Global Advanced Support Team - Senior Support Engineer. He can be reached via e-mail at charles.mclouth@centurasoft.com.

	Введите условия поиска Отправить форму поиска
	Web gupta.narod.ru

Return to http://gupta.narod.ru/