report.render(true) issue

Stimulsoft Reports.NET discussion
mmurdock
Posts: 94
Joined: Tue Mar 20, 2007 4:59 pm

report.render(true) issue

Post by mmurdock »

Does the new version require that I use core labs? If so what product?

Mat
Edward
Posts: 2913
Joined: Fri Jun 09, 2006 4:02 am

report.render(true) issue

Post by Edward »

We've tested our database pack with CoreLab version 4.50.26 and it was hard coded for use with CoreLab.

Also if you didn't use adapter from CoreLab, then also here is the link for version of our MySQL Database pack for free provider

MySQL Connector Net (we've tested our database pack with 5.2.1 version of this provider)

Thank you.
Attachments

[The extension mysqldatabase_mysqlnetconnector has been deactivated and can no longer be displayed.]

mmurdock
Posts: 94
Joined: Tue Mar 20, 2007 4:59 pm

report.render(true) issue

Post by mmurdock »

Thank you for create that new database pack. I have one questions in regard to that new database pack. In StiMysqlAdapterServer you have a couple of lines that look like this:

Code: Select all

        public override object GetMetadataProvider(IDbConnection connection)
        {
            return new Stimulsoft.Database.StiMySqlMetadataProvider(connection);

          
        }
Visual Studio throws the following error:

The type or namespace name 'StiMySqlMetadataProvider' does not exist in the namespace 'Stimulsoft.Database' (are you missing an assembly reference?)

I changed the code to look like this:

Code: Select all

        public override object GetMetadataProvider(IDbConnection connection)
        {
            //return new Stimulsoft.Database.StiMySqlMetadataProvider(connection);

            return new Stimulsoft.Database.StiSqlMetadataProvider(connection);
           
        }

Now it will compile. Was this just a coding mistake or is it something that I should be concerned about? I'm using Mysql Connector.net 5.2.2.

Thanks again,

Mat Murdock
Edward
Posts: 2913
Joined: Fri Jun 09, 2006 4:02 am

report.render(true) issue

Post by Edward »

Ok, we'll try to check this new version of Provider. With 5.2.1 version we haven't received this error.

Thank you.
Post Reply