Bug?

I have a .rdl file which I opened in visual studio 2005. I answered Yes to the prompt Microsoft Report Designer. . . Do you want to convert this file? [Yes] Then I saved the file.

The issue is when I am in Visual Studio and click on the Preview tab, I get the following error:

[rsErrorLoadingCodeModule] Error while loading code module: ‘x.ReportDefinitionsHelper, Version=1.0.0.0, Culture=neutral, PublicKeyToken=null’. Details: Could not load file or assembly 'AdvancedMD.Report.ReportDefinitionsHelper, Version=1.0.0.0, Culture=neutral, PublicKeyToken=null' or one of its dependencies. The system cannot find the file specified.

There was a <CodeModule> which existed prior to the conversion and the preview worked fine.

I tried to re-add the reference by clicking on the Layout tab then go to the report properties tab. Then, under references I clicked on the collection and browsed to the file which I wanted to reference and clicked ok, but I still get the error above when I click on the Preview tab. I tried to remove the reference save then come back in and add it again, but it still gives the error above.

The file I am trying to add to <CodeModule> (x.ReportDefinitionsHelper) references the following:

System

System.Data

System.Xml

Any help would be greatly appreciated.

Thanks

(I can load the .rdl to reporting services 2005 and go into Reporting Services Manager and view the report without any issues.)

I just had to move the file I was referenceing to the following location:

C:\Program Files\Microsoft Visual Studio 8\Common7\IDE\PrivateAssemblies

|||This solved the problem for me too. I have part of the VS2005 installed on my D: drive instead of the C: drive. But regardless of this I think it is strange that we have to put our own dll's in the MS directories. I would like to have them in my own project files. I think it is a bug since the VS2005 has a project structure, and it seems this does not fit in.|||

I had the same problem and however I have installed VS2005 in C: so that isn't the problem... the solution for me, as for TMK and Jelle, has been to put my dll in:

C:\Program Files\Microsoft Visual Studio 8\Common7\IDE\PrivateAssemblies

What i would like to know is the reason because of we have to put our dlls in that directory if in our references we specified another directory...

Can anyone explain it to us?

Bug?

I have a .rdl file which I opened in visual studio 2005. I answered Yes to the prompt Microsoft Report Designer. . . Do you want to convert this file? [Yes] Then I saved the file.

The issue is when I am in Visual Studio and click on the Preview tab, I get the following error:

[rsErrorLoadingCodeModule] Error while loading code module: ‘x.ReportDefinitionsHelper, Version=1.0.0.0, Culture=neutral, PublicKeyToken=null’. Details: Could not load file or assembly 'AdvancedMD.Report.ReportDefinitionsHelper, Version=1.0.0.0, Culture=neutral, PublicKeyToken=null' or one of its dependencies. The system cannot find the file specified.

There was a <CodeModule> which existed prior to the conversion and the preview worked fine.

I tried to re-add the reference by clicking on the Layout tab then go to the report properties tab. Then, under references I clicked on the collection and browsed to the file which I wanted to reference and clicked ok, but I still get the error above when I click on the Preview tab. I tried to remove the reference save then come back in and add it again, but it still gives the error above.

The file I am trying to add to <CodeModule> (x.ReportDefinitionsHelper) references the following:

System

System.Data

System.Xml

Any help would be greatly appreciated.

Thanks

(I can load the .rdl to reporting services 2005 and go into Reporting Services Manager and view the report without any issues.)

I just had to move the file I was referenceing to the following location:

C:\Program Files\Microsoft Visual Studio 8\Common7\IDE\PrivateAssemblies

|||This solved the problem for me too. I have part of the VS2005 installed on my D: drive instead of the C: drive. But regardless of this I think it is strange that we have to put our own dll's in the MS directories. I would like to have them in my own project files. I think it is a bug since the VS2005 has a project structure, and it seems this does not fit in.|||

I had the same problem and however I have installed VS2005 in C: so that isn't the problem... the solution for me, as for TMK and Jelle, has been to put my dll in:

C:\Program Files\Microsoft Visual Studio 8\Common7\IDE\PrivateAssemblies

What i would like to know is the reason because of we have to put our dlls in that directory if in our references we specified another directory...

Can anyone explain it to us?

Bug in SSIS?

I am trying to convert a string to a specific date format by using a simple select like this:

SELECT CONVERT(VARCHAR(3), CONVERT(DATETIME, ?, 103),107)

First of all the Parameter ? is not recognized and when i run the Preview it would trought the following error even if i change the ? with '20050101' for example:

===================================

There was an error displaying the preview. (Microsoft Visual Studio)

===================================

Undefined function 'CONVERT' in expression. (Microsoft JET Database Engine)

Program Location:

at Microsoft.SqlServer.Dts.Tasks.ExecuteSQLTask.Connections.SQLTaskConnectionOleDbClass.ExecuteStatement(Int32 resultType, Boolean isStoredProc, UInt32 dwTimeOut)
at Microsoft.DataTransformationServices.Design.PipelineUtils.ShowDataPreview(String sqlStatement, ConnectionManager connectionManager, Control parentWindow, IServiceProvider serviceProvider, IDTSExternalMetadataColumnCollection90 externalColumns)
at Microsoft.DataTransformationServices.DataFlowUI.DataFlowConnectionPage.previewButton_Click(Object sender, EventArgs e)

Anyone experiencing this kind of problem? Solutions?

Best Regards,

Luis Sim?es

Well the error clearly indicates that Jet doesn't support the function so this would not be an SSIS bug. Have you attempted to look at the Jet docs to see if it supports convert. The last time I used jet it did not.

Thanks,

Matt

|||

Yes you are right.

I have figured it out pretty quickly and i tried to delete this post without success sorry...

It was my mistake! Not really looking into it :P

But thanks :)

Best Regards,

PS: Merry Christmas to All of YOU!

Bug in Query Analyzer

Execute this in Query Analyzer:
SELECT CONVERT(varchar(8),0x0131) as A, 'X' as B
You will get the expected results if you choose "Results in text", but
if you choose "Results in grid" you will get nothing in column A and
'1' in column B.
Is there anyone at MS reading this ?
Is there any other place I should report this bug ?
Razvan Socol
I can report this as a bug. It does appear taht the grid does not return
the correct information, or atleast does not interpret it correctly.
Rand
This posting is provided "as is" with no warranties and confers no rights.
|||This inserts two characters into A: 0x01 and 0x31. 0x31 is, of course, an
ASCII '1'.
Now you know that 0x01 is the character that QA uses to separate columns
into the grid.
So, the grid has two columns defined by the select, but when populating the
columns QA sees three columns of data: NULL, '1', and 'X'. This causes the
final column of data not to have a home.
So, is this a bug? If Microsoft is willing to think so, that is great, but
I would consider this a behavior instead of a bug.
Russell Fields
"Razvan Socol" <rsocol@.fx.ro> wrote in message
news:60f52b8b.0406090141.7a9f61d7@.posting.google.c om...
> Execute this in Query Analyzer:
> SELECT CONVERT(varchar(8),0x0131) as A, 'X' as B
> You will get the expected results if you choose "Results in text", but
> if you choose "Results in grid" you will get nothing in column A and
> '1' in column B.
> Is there anyone at MS reading this ?
> Is there any other place I should report this bug ?
> Razvan Socol
|||I definitely think that it's a bug. I specifically simplified the
query to this form (the situation I encountered was more complex). I
understood all that you explained before I posted, but it's good that
you did explain it, so that other readers understand.
Razvan
"Russell Fields" <RussellFields@.NoMailPlease.Com> wrote:
> This inserts two characters into A: 0x01 and 0x31. 0x31 is, of course, an
> ASCII '1'.
> Now you know that 0x01 is the character that QA uses to separate columns
> into the grid.
> So, the grid has two columns defined by the select, but when populating the
> columns QA sees three columns of data: NULL, '1', and 'X'. This causes the
> final column of data not to have a home.
> So, is this a bug? If Microsoft is willing to think so, that is great, but
> I would consider this a behavior instead of a bug.
> Russell Fields