PDA

View Full Version : crystal reports crystl16.ocx



NewsArchive
02-14-1997, 01:00 AM
Given situation wfw3.11 or in win95 :

I.S. export prof. does'nt register the crystal ocx while installing.

The VB dll's and ocx's are registered correctly.

Please, it's urgent.

Alex Vandereycken
ASQ - Belgium.
__________________________________
private email : vandereycken@hotmail.com
work email :alex.vandereycken@asq.be

NewsArchive
02-15-1997, 01:00 AM
Hi Alex,

Regarding..
>>>>
I.S. export prof. does'nt register the crystal ocx while installing.
<<<<

If you select the Crystal Reports InstallShield Object for a 16-bit setup,
Express will add the file Crxlat16.dll to your System Files - WinSysDir
group. The correct filename is Crxlate.dll. This has been corrected for the
Professional Edition.

To work around this, first go to the Groups and Files dialog and delete
Crxlat16.dll from the System Files - WinSysDir group. Then launch Explorer
and drag and drop Crxlate.dll from your Windows System directory into the
System Files - WinSysDir group.

If you still have queries you can send it to us with details.

Regards,

Mohan K M K,
Aditi Corp.

InstallShield Corporation Authorized Solution Provider.

Aditi Corp was formerly known as NetQuest Inc.

NewsArchive
05-22-1997, 12:00 AM
Greetings,

I too had many problems getting CRystl16.OCX to register on WIn3.1
machines. Here's what I did to solve the problem:

1) modified swdepend.ini to look like this:

[CRYSTL16.OCX]
Register=$(DLLSelfRegister)

[CRYSTL16 OCX]
Src=<WINSYS16DIR>
Uses1=CRYSTL16.OCX
Uses2=CRPE.DLL
Uses3=CRXLATE.DLL
Uses4=uxddisk.dll
Uses5=uxfdif.dll
Uses6=uxfrec.dll
Uses7=uxfsepv.dll
Uses8=uxftext.dll
Uses9=pdbdao.dll
Uses10=pdctdao.dll
Uses11=pdirdao.dll
Uses12=pdsodbc.dll
Uses13=PDBBND.DLL
Uses14=MFCOLEUI.DLL

Note that the first entry has a "." between the filename and the
extension, while the second does not. This is Very Important (and was the
source of all my problems)! The first entry tells InstallShield to
register this file, while the second lists all of the files that accompany
the file.
Note also that I added the file MFCOLEUI.DLL.

2) added a group to my InstallShield setup; called it Crystal OCX, and
moved the Crystl16.OCX into it. This had the effect of making this OCX be
the last file installed on the system.

This solved the problem. Good luck!

Steve Locke
HBO & Company, Inc
slocke@hboc.com

eu002053 <asq@pophost.eunet.be> wrote in article
<01bc1a86$7bb17ae0$55d84ac1@asqpc79>...
> Given situation wfw3.11 or in win95 :
>
> I.S. export prof. does'nt register the crystal ocx while installing.
>
> The VB dll's and ocx's are registered correctly.
>
> Please, it's urgent.
>
> Alex Vandereycken
> ASQ - Belgium.
> __________________________________
> private email : vandereycken@hotmail.com
> work email :alex.vandereycken@asq.be
>
>

NewsArchive
11-21-1997, 01:00 AM
Hey Steve, thanks, this really helped me when I needed it.

One point to all: the SWDEPEND.INI file is the one in the OBJS\VB4
directory (if using Installshield Express)--not the one in the Windows
directory. Also, you may have to use a text editor on the .IWZ (or
whatever) file to put and keep CRYSTL16.OCX as the last group and/or file
installed--as otherwise it always put's the System Files group as the last
one.

Steve Locke <locke@hboc.com> wrote in article
<01bc66b2$a9f419d0$82201595@pcstevel>...
> Greetings,
>
> I too had many problems getting CRystl16.OCX to register on WIn3.1
> machines. Here's what I did to solve the problem:
>
> 1) modified swdepend.ini to look like this:
>
> [CRYSTL16.OCX]
> Register=$(DLLSelfRegister)
>
> [CRYSTL16 OCX]
> Src=<WINSYS16DIR>
> Uses1=CRYSTL16.OCX
> Uses2=CRPE.DLL
> Uses3=CRXLATE.DLL
> Uses4=uxddisk.dll
> Uses5=uxfdif.dll
> Uses6=uxfrec.dll
> Uses7=uxfsepv.dll
> Uses8=uxftext.dll
> Uses9=pdbdao.dll
> Uses10=pdctdao.dll
> Uses11=pdirdao.dll
> Uses12=pdsodbc.dll
> Uses13=PDBBND.DLL
> Uses14=MFCOLEUI.DLL
>
> Note that the first entry has a "." between the filename and the
> extension, while the second does not. This is Very Important (and was
the
> source of all my problems)! The first entry tells InstallShield to
> register this file, while the second lists all of the files that
accompany
> the file.
> Note also that I added the file MFCOLEUI.DLL.
>
> 2) added a group to my InstallShield setup; called it Crystal OCX, and
> moved the Crystl16.OCX into it. This had the effect of making this OCX
be
> the last file installed on the system.
>
> This solved the problem. Good luck!
>
> Steve Locke
> HBO & Company, Inc
> slocke@hboc.com
>
> eu002053 <asq@pophost.eunet.be> wrote in article
> <01bc1a86$7bb17ae0$55d84ac1@asqpc79>...
> > Given situation wfw3.11 or in win95 :
> >
> > I.S. export prof. does'nt register the crystal ocx while installing.
> >
> > The VB dll's and ocx's are registered correctly.
> >
> > Please, it's urgent.
> >
> > Alex Vandereycken
> > ASQ - Belgium.
> > __________________________________
> > private email : vandereycken@hotmail.com
> > work email :alex.vandereycken@asq.be
> >
> >
>