Packaging VB 6.0 with Crystal report Control

Dear All,

Pls give reply for this problem,this is the last helping source for me,so pls don't leave me without solutions.

I have a problem,pls help me .

I have created the front end application in V.B 6.O and Back end in Sql 2K and iam generating report using Crystal Report 8.5.
Our OS is windows 2k professional.\
My problem is I generated report using Crystal report as a Blank report and called in VB by adding the component Crystal report Control(Crystl32.ocx)

My Problems
1. Iam not able package my Vb application because it is showing Crystl32.ocx file can’t be registered, if I remove this control from VB I can create the package .
2. So I done another way ,by making exe of my VB application ,then create a new project and add all controls I used in my application except Crystal report Control, then I made package of this Project ,then I run the exe file in another computer and also installing the package that I created so that I can use runtime of VB,it is working fine accept reports.if the forms contain any report it gives error like this : Run-time error ‘339’ ,Component Crystl32.ocx or one of its dependencies not correctly registered a file is missing or invalid.
3. So while I add crystal report control I can’t run the application ,so I copied the file Crystl32.ocx and dumped to another machine system32 folder and tried to run “regsvr32 with the path where I stored the file”, while I run this iam getting error like this “LoadLibrary (“C:\i386\system32\Crystl32.ocx”) failed-The specified module could not be found”.
4. so can u help me for that ,I want to run this application in 90 users, this projects related to school attendance register

I will be very Thank full to u all ,if u provide me a solution for this,iam new to Crystal report and my client needs report to be generated in CR.So pls give me a solution for this.

With regards

SaijuRemove Crystal report components then create package for your application. If the process became successful then, ad the components back and make new exe file
Copy new exe file over the one installed at the client machine.
hop this would help you|||Thank u this helped me.
I made the exe & run in all the client computers

Thanks for the reply

SaijuMammen

Package failure still causing partial load

I have a package that is failing because of a truncation error. Now, by default (and I leave this for ALL my packages) if one row fails processing the entire package should fail and nothing gets loaded into db. But instead I am actually getting a partial db load.

I have confirmed the "Rows per btach" value (blank) and the "Maximum insert commit size" value (0) for the OLE DB Destination Editor so I have no idea what is going on. Are there any other properties I should be checking?

Thanks.

Jason

Why are you surprised that there is a partial load? You'll have to set MICS to equal to or greater than the number of rows coming into the source to have it such that if one row is bad, the whole batch is aborted.

The settings you have now are likely committing each row as they are inserted.|||According to the documentation, a "value of 0 indicates that all data is committed in a single batch after all rows have been processed". This, to me, tells me that all rows will be written or none. Since I am getting a truncation error, should I not be getting zero rows written?|||Well, I'm not so sure that SQL Server can accept an arbitrarily large bulk load. That is, I believe there's a limit to the size of the batch, and if it's exceeded, it will have to issue a commit or fail. I'm not sure.

You could redirect error rows out of the OLE DB command and try to see where that error occurs (row number or something).|||

Thanks for the responses Phil.

I know exactly where the error is happening. Just that in the past (with other packages) the execution loaded everything or nothing. (No matter the number of rows in the source.) It is just that the behavior for this package is not what I am used to and I cannot figure out why it is doing a partial load when the settings (as far as I can tell) are telling it not to.

- Jason

|||

To be honest, I have been playing with those 2 properties in the OLE DB Destination, so I can get bigger batches but I only can get around 9K-10K rows per commit as maximum. Not sure if SSIS or Bulk_insert look at the available resources and decided what value to use. I have no gotten the time to dig into that.

|||

Rafael Salas wrote:

To be honest, I have been playing with those 2 properties in the OLE DB Destination, so I can get bigger batches but I only can get around 9K-10K rows per commit as maximum. Not sure if SSIS or Bulk_insert look at the available resources and decided what value to use. I have no gotten the time to dig into that.

I think that SQL Server can only handle a batch size of 256 MB.

http://msdn2.microsoft.com/en-us/library/ms143432.aspx