Importing Access Reports

I am trying to import access reports from an Access 2003 database. I am
getting two different errors, and none of the reports are being imported.
The first error is:
An error occurred while the report DailySales was being imported:
Reserved Error
The second error is:
An error occurred while the report Report: Weekly was being imported: The
given path's format is not supported.
I believe the second error is due to the naming convention not allowing ":"
in the name, but I do not know how to fix the first error.
Any suggestions?The first error could be coming from Access. Could you try the following?
Open your database in Microsoft Access. Create a new Module and paste the
following code into it:
Sub Export()
Application.ExportXML ObjectType:=acExportReport, _
DataSource:="DailySales ", _
ImageTarget:=".", _
PresentationTarget:="DailySales .xsl", _
OtherFlags:=acPersistReportML
End Sub
Set the cursor at the beginning of the Sub and click the Run button. If
ExportXML succeeds, it should create a file called "DailySales_report.xml"
in your "My Documents" folder. If you can send the file to me, I'll look at
it. If ExportXML fails, then it's an Access problem. You could try the
Access newsgroups for help.
--
Albert Yen
SQL Server Reporting Services
This posting is provided "AS IS" with no warranties, and confers no rights.
"Ben" <ben_1_ AT hotmail DOT com> wrote in message
news:68663BEB-7AD6-4A4B-A263-A3D4D86FAE48@.microsoft.com...
>I am trying to import access reports from an Access 2003 database. I am
> getting two different errors, and none of the reports are being imported.
> The first error is:
> An error occurred while the report DailySales was being imported:
> Reserved Error
> The second error is:
> An error occurred while the report Report: Weekly was being imported:
> The
> given path's format is not supported.
> I believe the second error is due to the naming convention not allowing
> ":"
> in the name, but I do not know how to fix the first error.
> Any suggestions?|||Thank you Albert. I know the reports work because they reside in a database
we use on a frequent basis and run the reports. Tommorow when I get into the
office, I will try your solution. If the reports do generate the .xml file,
where should I email it to so you can look at it?
I have a feeling my visual studio .net install is corrupt, so before i try
your solution, I am going to uninstall everything and do a fresh install. I
am also having a problem using mdb files as datasources (visual studio
crashes when adding tables to a query), so maybe my errors are connected. I
did however try creating a blank report with just a label in the header, and
I still got the same error.
Thanks again,
Ben
"Albert Yen [MSFT]" wrote:
> The first error could be coming from Access. Could you try the following?
> Open your database in Microsoft Access. Create a new Module and paste the
> following code into it:
> Sub Export()
> Application.ExportXML ObjectType:=acExportReport, _
> DataSource:="DailySales ", _
> ImageTarget:=".", _
> PresentationTarget:="DailySales .xsl", _
> OtherFlags:=acPersistReportML
> End Sub
> Set the cursor at the beginning of the Sub and click the Run button. If
> ExportXML succeeds, it should create a file called "DailySales_report.xml"
> in your "My Documents" folder. If you can send the file to me, I'll look at
> it. If ExportXML fails, then it's an Access problem. You could try the
> Access newsgroups for help.
> --
> Albert Yen
> SQL Server Reporting Services
> This posting is provided "AS IS" with no warranties, and confers no rights.
> "Ben" <ben_1_ AT hotmail DOT com> wrote in message
> news:68663BEB-7AD6-4A4B-A263-A3D4D86FAE48@.microsoft.com...
> >I am trying to import access reports from an Access 2003 database. I am
> > getting two different errors, and none of the reports are being imported.
> >
> > The first error is:
> > An error occurred while the report DailySales was being imported:
> > Reserved Error
> >
> > The second error is:
> > An error occurred while the report Report: Weekly was being imported:
> > The
> > given path's format is not supported.
> >
> > I believe the second error is due to the naming convention not allowing
> > ":"
> > in the name, but I do not know how to fix the first error.
> >
> > Any suggestions?
>
>|||You can just attach the file to your newsgroup post. If you are unable to
do that, you can get my email address from this message. Just remove the
string "online."
--
Albert Yen
SQL Server Reporting Services
This posting is provided "AS IS" with no warranties, and confers no rights.
"Ben" <ben_1_ AT hotmail DOT com> wrote in message
news:4D58444F-CD86-4F1B-A028-7096C27A0FEC@.microsoft.com...
> Thank you Albert. I know the reports work because they reside in a
> database
> we use on a frequent basis and run the reports. Tommorow when I get into
> the
> office, I will try your solution. If the reports do generate the .xml
> file,
> where should I email it to so you can look at it?
> I have a feeling my visual studio .net install is corrupt, so before i try
> your solution, I am going to uninstall everything and do a fresh install.
> I
> am also having a problem using mdb files as datasources (visual studio
> crashes when adding tables to a query), so maybe my errors are connected.
> I
> did however try creating a blank report with just a label in the header,
> and
> I still got the same error.
> Thanks again,
> Ben
> "Albert Yen [MSFT]" wrote:
>> The first error could be coming from Access. Could you try the
>> following?
>> Open your database in Microsoft Access. Create a new Module and paste the
>> following code into it:
>> Sub Export()
>> Application.ExportXML ObjectType:=acExportReport, _
>> DataSource:="DailySales ", _
>> ImageTarget:=".", _
>> PresentationTarget:="DailySales .xsl", _
>> OtherFlags:=acPersistReportML
>> End Sub
>> Set the cursor at the beginning of the Sub and click the Run button. If
>> ExportXML succeeds, it should create a file called
>> "DailySales_report.xml"
>> in your "My Documents" folder. If you can send the file to me, I'll look
>> at
>> it. If ExportXML fails, then it's an Access problem. You could try the
>> Access newsgroups for help.
>> --
>> Albert Yen
>> SQL Server Reporting Services
>> This posting is provided "AS IS" with no warranties, and confers no
>> rights.
>> "Ben" <ben_1_ AT hotmail DOT com> wrote in message
>> news:68663BEB-7AD6-4A4B-A263-A3D4D86FAE48@.microsoft.com...
>> >I am trying to import access reports from an Access 2003 database. I am
>> > getting two different errors, and none of the reports are being
>> > imported.
>> >
>> > The first error is:
>> > An error occurred while the report DailySales was being imported:
>> > Reserved Error
>> >
>> > The second error is:
>> > An error occurred while the report Report: Weekly was being imported:
>> > The
>> > given path's format is not supported.
>> >
>> > I believe the second error is due to the naming convention not allowing
>> > ":"
>> > in the name, but I do not know how to fix the first error.
>> >
>> > Any suggestions?
>>|||It seems the "given path is not supported" error comes from the name having
either semi colons (:) or ampersands (&). Now i get reserved errors and item
already added errors...
"Albert Yen [MSFT]" wrote:
> You can just attach the file to your newsgroup post. If you are unable to
> do that, you can get my email address from this message. Just remove the
> string "online."
> --
> Albert Yen
> SQL Server Reporting Services
> This posting is provided "AS IS" with no warranties, and confers no rights.
> "Ben" <ben_1_ AT hotmail DOT com> wrote in message
> news:4D58444F-CD86-4F1B-A028-7096C27A0FEC@.microsoft.com...
> > Thank you Albert. I know the reports work because they reside in a
> > database
> > we use on a frequent basis and run the reports. Tommorow when I get into
> > the
> > office, I will try your solution. If the reports do generate the .xml
> > file,
> > where should I email it to so you can look at it?
> >
> > I have a feeling my visual studio .net install is corrupt, so before i try
> > your solution, I am going to uninstall everything and do a fresh install.
> > I
> > am also having a problem using mdb files as datasources (visual studio
> > crashes when adding tables to a query), so maybe my errors are connected.
> > I
> > did however try creating a blank report with just a label in the header,
> > and
> > I still got the same error.
> >
> > Thanks again,
> > Ben
> >
> > "Albert Yen [MSFT]" wrote:
> >
> >> The first error could be coming from Access. Could you try the
> >> following?
> >> Open your database in Microsoft Access. Create a new Module and paste the
> >> following code into it:
> >>
> >> Sub Export()
> >>
> >> Application.ExportXML ObjectType:=acExportReport, _
> >> DataSource:="DailySales ", _
> >> ImageTarget:=".", _
> >> PresentationTarget:="DailySales .xsl", _
> >> OtherFlags:=acPersistReportML
> >> End Sub
> >>
> >> Set the cursor at the beginning of the Sub and click the Run button. If
> >> ExportXML succeeds, it should create a file called
> >> "DailySales_report.xml"
> >> in your "My Documents" folder. If you can send the file to me, I'll look
> >> at
> >> it. If ExportXML fails, then it's an Access problem. You could try the
> >> Access newsgroups for help.
> >>
> >> --
> >> Albert Yen
> >> SQL Server Reporting Services
> >>
> >> This posting is provided "AS IS" with no warranties, and confers no
> >> rights.
> >>
> >> "Ben" <ben_1_ AT hotmail DOT com> wrote in message
> >> news:68663BEB-7AD6-4A4B-A263-A3D4D86FAE48@.microsoft.com...
> >> >I am trying to import access reports from an Access 2003 database. I am
> >> > getting two different errors, and none of the reports are being
> >> > imported.
> >> >
> >> > The first error is:
> >> > An error occurred while the report DailySales was being imported:
> >> > Reserved Error
> >> >
> >> > The second error is:
> >> > An error occurred while the report Report: Weekly was being imported:
> >> > The
> >> > given path's format is not supported.
> >> >
> >> > I believe the second error is due to the naming convention not allowing
> >> > ":"
> >> > in the name, but I do not know how to fix the first error.
> >> >
> >> > Any suggestions?
> >>
> >>
> >>
>
>