ExportModeller.dll !!??!??!

VB6, CR9, building on Win2k box, deploying on varying OS boxes.


After not being able to get the printer to print characters anyone could understand, Crystal Decisions has told me to export the .rpt to PDF.

I HAVE GOT A REPORT I CAN USE !!! (in the IDE)
(I fall asleep waiting for it, but hey...it eventually prints)

Now, when I distribute the app, using the package and deployment wizard, onto a Win98 box I get an error registering the ExportModeller.dll....

The Crystal Decisions site, says there is an issue with the atl.dll with Win2k and Win98...(cant use the same one!?)

So they suggest I use the Visual Studio Installer....which I dont have... :(

So, since I have invested thousands here to UPGRADE to CR9, to have my project delayed in deploying...

I am wondering if anyone else has worked around this issue using something other than the VSI....

I will use VSI, if that is my only option...but I would value any advice from the experts here...before I just assume Crystal Decisions is correct... :rolleyes:

Try inno http://www.jrsoftware.org/isinfo.php

Inno can determine which os your are installing to and then copy the correct alt.dll


From one of my setup scripts

Code:

---

; Atl.dll must be register before the crystal files exportmodeller.dll and crtslv.dll.  NOTE: There are two verion of Atl.dll.
Source: "c:\Inno Scripts\crystalInstall\prior2000\Atl.DLL"; DestDir: "{sys}"; Flags: uninsneveruninstall sharedfile regserver; OnlyBelowVersion: 0,5.0
Source: "c:\Inno Scripts\crystalInstall\2000\Atl.DLL"; DestDir: "{sys}"; Flags: uninsneveruninstall sharedfile regserver; MinVersion: 0,5.0

---

Thanks for the reply.

Thanks for the script. Since I am unfamiliar with INNO (although heard some talk about it), and you mention the scripting here...

Am I going to have to learn a new scripting language to do all of this, it looks like it has a wizard like P&D, does it walk you through dependencies..?

I really appreciate your help on this, wrapping this phase of the project is only being held up by Crystal...so if I can master this, I can move on...:D

"Am I going to have to learn a new scripting language to do all of this, it looks like it has a wizard like P&D, does it walk you through dependencies"

No, but you can get most of the required information by running P&D and looking at the setup.lst (I think this is the correct name.)


Look at these links:

http://www.visualbasicforum.com/show...t=tmp%2A+files

http://www.jrsoftware.org/ishowto.phtml?a=vb

Also, runtime.hlp will provide you with all the crystal files you will need.


What database are you using?

Make sure you get the latest hot fixes from crystal.

Ken!

You are a life saver...(I think)....!

I have new life..lots of reading here and experimenting, but what I have been working with is working so far THANKS!! :D

Got all of the Crystal files from the Runtime.chm (except the prior2000 version of atl.dll....where is the best to pick that up?)

Database:
Access.mdb using JET OLEDB 4.0, have been distributing MDAC_TYP.exe with the app. and I noticed the second post from the first link you sent, I will look that over for the issues with this, if any.

Question:
Rather newbieish, I imagine, but is there a way to bring a script you have already created back into the wizard, for fine tuning etc? I ran through the first time, and kinda skipped over the Installation text files etc. I can go in and hand code, now that I see what is going on....but it would be easier, here and there if I could add a file, etc. through the wizard.

Cant tell you how much I appreciate this !!
The FIRST forward progress on this part of the project in a week !!
:D

The two alt.dll should be on the crystal cd.

I'm using 8.5 and the locations are

D:\Windows\System32\Redist\MS\System (for unicode version for NT/2000 computers)

D:\Windows\System32\Redist\MS\System\ANSI (for 9x computers)

I can not help you with P&D questions, its been a few years since I used it.

Here's an inno script for one of my apps. It's for crystal 8.5, so some of the crystal stuff may need to be changed. But you can use most of it.

Thanks for the file !

Questions, Questions, Questions ??

I notice you are using the vbRun6sp5.exe at the end, and it doesnt look like it is checking for same/older version (as mentioned in the link)...not knocking it, just wondering why the difference, if important?

By using the {sys}, I am guessing this is placing the files in the system directory (Crystal Report files)...where before I was creating a directory under Program Files\Common Files\Crystal to place these...is there an easy way to do this, I hate to keep throwing things in the system directory and Crystal mentions to use the Program\Common...?

Thanks for the help on atl...guess my brain is too excited about making some progress, to think of the obvious... :D

was unclear on the wizard question, sorry....wasnt talking about Micro$oft P&D wizard...talking about INNO wizard....(but it is really no biggie)...

Thank you again!

"I notice you are using the vbRun6sp5.exe at the end, and it doesnt look like it is checking for same/older version (as mentioned in the link)...not knocking it, just wondering why the difference, if important?"

Read http://support.microsoft.com/default...NoWebContent=1 about vbRun6sp5.exe. This file installs most of the files that are required to run an application written in vb. You will only need to include any addons like msflexgrid. vbRun6sp5.exe will check to see if there is a newer file and all of that good stuff.

"was unclear on the wizard question, sorry....wasnt talking about Micro$oft P&D wizard...talking about INNO wizard....(but it is really no biggie)."

Just start a new inno project and replace any thing in it with my stuff. Then make the modifications to it.

"By using the {sys}, I am guessing this is placing the files in the system directory (Crystal Report files)...where before I was creating a directory under Program Files\Common Files\Crystal to place these...is there an easy way to do this, I hate to keep throwing things in the system directory and Crystal mentions to use the Program\Common...?"

First I heard of it, but it's looks like your right.
http://support.crystaldecisions.com/...s/c2013175.asp

I will have to look into it.

Thanks again for the responses..

well, I seem to have built the setup script, somewhat successfully...

I deployed the application to a Win98 machine, and most everything seems to be working fine....

EXCEPT,
Crystal Reports is asking for UNICOWS.dll...
now this would be a good place to insert a farmer joke of your choosing, but I will resist...

so, hoping I could shoot from the hip, I have downloaded the unicows.exe from the micro$oft sight, and have included it in my setup as a component, the same way you addressed MDAC_TYP.exe...

am I close?

Did you not have to worry about Unicows, when you deployed, because I dont see any reference in your setup..??

Since I am currently using 8.5, my apps don't need UNICOWS.dll.

As per Crystal http://support.crystaldecisions.com/...s/c2011871.asp you will want to install it only if the os is 9x/me.

;Windows versions:
;4.0.950 Windows 95
;4.0.1111 Windows 95 OSR 2 & OSR 2.1
;4.0.1212 Windows 95 OSR 2.5
;4.1.1998 Windows 98
;4.1.2222 Windows 98 Second Edition
;4.9.3000 Windows Me
;
;Windows NT versions:
;4.0.1381 Windows NT 4.0
;5.0.2195 Windows 2000
;5.01.2600 Windows XP

I just realized that I have a problem with the way I am using MinVersion and OnlyBelowVersion: From Inno help:

Format: a.bb,c.dd, where a.bb is the Windows version, and c.dd is the Windows NT version.
Default value: 4,4

Description:
This directive lets you specify a minimum version of Windows or Windows NT that your software runs on. To prevent your program from running on Windows or Windows NT, specify "0" for one the minimum versions. Build numbers and/or service pack levels may be included in the version numbers.

I did not realized that the first parameters was for windows and the second was for nt.

I have to go out for a few hours, when I get back, I will attached a corrected script.

For UNICOWS.dll, use OnlyBelowVersion: 5.0,0

I appreciate the help, and will wait for the corrected script. Since I think I am getting the hang of INNO, but dont want to make any wrong moves at this point.

What is your opinion on the Unicows.dll/Unicows.exe... do you think I just need to distribute the .dll ? Crystal paperwork says I have to get it from M(big brother)soft, and when I go to the site all I find is the .exe...

Everything seems to be working well with INNO (THANKS for the tip!!)

It just keeps bombing on the reporting aspects...

Here's the corrected inno script. I will test it on Thursday on a clean 98 and xp home machine. I will need to do a factory install on both machines before hand.

I think you would want to copy the exe on to the user pc and run it from there, just like MDAC.

"It just keeps bombing on the reporting aspects"

???

Are you using rdc and the report viewer?

Ok, updated my script to match yours.

Added the Unicows.exe, after copying all the MDAC stuff and changing to the applicable Unicow.

On W98:
As it is going through the install, a box comes up stating it is installing MDAC, however, I do not get one for Unicow.
When I prompt for "Restart", I recieve a blue screen Fatal Error.
When it finally restarts, I get a message box, stating:
Crystal Decisions
The Micro$oft Layer for Unicode (unicows.dll) could not be found. This program will now exit.

When I do a search on the machine, it does not see a unicow* ... so that leads me to believe the install is not successful (either the .exe or the .dll)

When I try to run the report, it states ActiveX cannot create the control.

On Win2k:
Everything seems to go fine, although it appears the MDAC is executing...and not sure it should ?

No error messages on reboot.

When I try to run the report, I get an error:
Runtime Error '-2147190548(800478ec)':
Error in file ??":
Missing or out-of-date Export Dll.

As for my printing method.
No - CRViewer.
I dont believe I am using RDC.

The attached txt is my print command, which works inside the IDE. Simply creating a PDF file, from a .RPT premade.

Believe me, your help on this has been more than you can imagine...and I am really liking this INNO, probably wont get me to shut up about it....

Would be interested in ANYTHING you have to comment on..

"On Win2k:
Everything seems to go fine, although it appears the MDAC is executing...and not sure it should ?"

What version of MDAC are you installing?

If you are installing 2.6 and above, it should install on 2000.

From MSDN - MDAC Installation

"As mentioned earlier, Windows Me, Windows 2000, and Windows XP all hold MDAC core components as Windows File Protection files. Because of this, updates to MDAC are considered OS upgrades on these systems. Over time, service packs have been released to the various MDAC versions. MDAC service pack installation installs the entire MDAC stack on a computer; MDAC service packs are not incremental patches, as is the case with some products. Therefore, you do not need to install MDAC 2.6 before you install MDAC 2.6 SP1, for example.

MDAC 2.5 is pre-installed in Windows Me and Windows 2000. There is no way to install a version of MDAC that is earlier than MDAC 2.5 on computers that are running these operating systems. In addition, you must use OS service packs to install MDAC 2.5 SP1 and SP2 on Windows 2000 and Windows Me. For example, Windows 2000 SP1 contains MDAC 2.5 SP1 and Windows 2000 SP2 contains MDAC 2.5 SP2. At the time of this article's publication, there are no service packs for Windows Me; therefore, no MDAC 2.5 service packs can be applied to these systems. On computers that are running either Windows Me or Windows 2000, you can apply MDAC 2.6 and later directly without the need for an OS service pack.

MDAC 2.7 RTM is pre-installed in Windows XP; because the MDAC files are Windows File Protection files, MDAC 2.7 RTM is the earliest version that you can install on Windows XP."

I would use 2.7.


I did a search on http://www.jrsoftware.org/newsgroups.php#search for unicows.dll. This is the archives for the inno newsgroup. This link may help:
http://news.jrsoftware.org/news/innosetup/msg21087.html

If not, do another search, there were a lot of hits.


"Missing or out-of-date Export Dll."

These may help http://support.crystaldecisions.com/...d=74&mid=97774

http://support.crystaldecisions.com/...s/c2012282.asp

If not, you are most likey missing a dll. You will have to check the runtime help file.

Good luck.

Ken!

Thanks.

Did searches on the Crystal site for unicows and nothing came up as valuable as what you sent !

And for whatever reason (FRUSTRATION probably) didnt search on the "missing dll" But from the sounds of it, your post may have answered my question !

I will give this a try, after thorough reading.....and double checking on my dll, inclusions...

sorry for the mistake on MDAC, you are correct.

Thanks again, you have helped keep me sane....

FYI

I have walked through the post information, regarding Unicows.dll, etc for W98....done each of the items listed....and the UNICOW issue seems to have gone away...

However, now when I try to print the report, I get the following:
"Invalid TLV record"

I have tried my report, as suggested on the CR site, and everywhere it seems to work fine (except the deployed machine, which I cant get to the report)...so I dont think it is a corupt .RPT file.


The W2k box is continuing to give me the same error. I have walked through the DLL's, and changed the VB script to the suggestion. However, I am receiving the same error.

I have contacted Crystal again for assistance, but will probably only receive the same answer I got before

"I suggest you to ignore the error messages and continue deploying the application and let me know what you find."

(Actual advice from Crystal Decisions)

Anyone with any advice on this issue, or other links not mentioned here, I would be more than appreciative.....

:(

"Invalid TLV record"

Look at:

http://support.crystaldecisions.com/...d=77&mid=84867

Thanks once again, Ken....

Todays update, (for everyone who comes across this)....

The TLV error seemed to be caused by:
msvcp60.dll (system file)
msvcrt.dll(system file)

Which crqe.dll is dependent on (you were again ON THE MARK..Ken) the crqe.dll file was there, but nowhere was there documentation telling me to check for the others...

Now, I am getting the following error....when I try to run the report:
Logon Failed
Details: Error Code 0x800401f3

This is the W98 machine, I am depolying to.

The W2k machine is still in the:
Error in file ??
Missing or out-of-date dll

Which, Crystal has been so kind to tell me about Modules.exe (run a search on the Crystal Decisions site) which will compare the two machines and tell you what is different (dll wise)...
This is going to take some time, cause there are a few there, and who knows which one Crystal is dependent on!

I am telling you! When I get to the end of this, I will take the time to document and create whatever I can to assist....

cause i dont wish this on anyone....!!

Try http://support.crystaldecisions.com/...s/c2011521.asp

Thank you again....Ken...

I gotta give you an A++++ for hanging in there with me...

and for your efforts...

Because this is a Access2000 db, without passwords, I am not sure it is a permission issue.

I am using the following to run the print command...


Private Sub cmdPrint_Click()
Dim objApp As CRAXDRT.Application
Dim objReport As CRAXDRT.Report
Dim objExportOptions As CRAXDRT.ExportOptions
Dim objTable As CRAXDRT.DatabaseTable
Dim Cap1 As String

MousePointer = vbHourglass

Set objApp = New CRAXDRT.Application
Set objReport = objApp.OpenReport(App.Path & "\Db\MyReport.rpt")

With objReport
Set objExportOptions = .ExportOptions
With objExportOptions
.DestinationType = crEDTDiskFile
.DiskFileName = App.Path & "\Temp\MyReport.pdf"
.FormatType = crEFTPortableDocFormat
.PDFExportAllPages = True
End With
.ReadRecords
.DisplayProgressDialog = False
.Export (False)
End With

frmPdf.Visible = True
Call PDFView

MousePointer = vbNormal

Set objTable = Nothing
Set objExportOptions = Nothing
Set objReport = Nothing
Set objApp = Nothing
Exit Sub

Now, I am under the impression, because the .rpt is linked to the mdb directly...that I dont need to open the connection..

That is how I did it in the past (before all this).

This stands by itself (not on a network) the DB dir is directly on the app.path, and this db is only used by this user...

I use the database to hold info for a listview (on this form), which then I give the user an option to print the info...

I checked and double checked to make sure the connection and recordset are closed and set to "nothing" when I was done filling the listview....so NO other sources should be using the database.

So, I dont think it could be a sharing violation (with the .rpt)...

so cant think of what else would be causing this, with reference to the article you linked....

Did I miss checking something?

**update**

For those of you interested or following:

After contacting CR support, I was told the following (which I could not really find documented clearly)
-------------------------------------------------
"There are basically two types of export dlls:

u2d* - these are the export destination dlls, eg, exporting to disk,
exporting to application u2f* and crxf* - these are the export format dlls

The dlls that start with crxf* are dependent on both crtslv.dll and
exportmodeller.dll.

If you only have the export format dlls and not the destination dlls or vice versa, then it would result in the 'Missing or out-of-date Export Dll'. You need to distribute both export and destination dlls."
------------------------------------------------

In which case, I went through the runtime.chm, one more time, to find the required export dll's. (Look at EVERYTHING that has to do with exporting.) I could not find a number of the DLL's loaded on my machine and inquired with CR about that.

-------------------------------------------
The response was:

"Not all the export dlls get installed by default. In order to get every single export dlls, you have to do a custom install and check every single option you see under the export section."

"To answer your question, yes, there is a lot of dlls you need to gather up if you choose to do a manual installation. This is why we came up with merge modules. These msm files include all the runtime files, and it makes deployment much simpler. The one disadvantage to this approach is that it will put a lot of dlls on the client machine, and half of them you probably do not need."
----------------------------------------

I am still working on getting the deployment to work at this point, but at least at this point, I am getting the same Logon Failed error on both machines.


For what it is worth, hope this helps someone out there.

well,

here it is... (the solution I came up with)..

for what it is worth.

course, if you got this far...you may be tired of reading...

or ready to give up !


http://www.vbforums.com/showthread.p...hreadid=252120

For anyone who still needs this, I went around and around with this problem.

One day I did a search on the dll's required for the exporting and I discovered two sets of dll's. One in the usual crystal folders and one in the service pack folder.

Once I included both of these drivers in my install package everything worked like a charm.

:bigyello:

Also, if you have troubles getting the dll's you want where you need then using the VB 6 Package and deployment wizard, I suggest you use the Visual Studio Installer.

http://msdn.microsoft.com/vstudio/do...s/tools/vsi11/