How to run Reporting service in MS-Access environment?

Hi

Please someone tell me, is it possbile to run Reporting service in MS-Access environment?
I mean to say i have to use MS-Access as user interface to design and generate report
(instead of Visual studio IDE) and the Sql server 2005 should be Report Server.
If it is possible then how can i implement it.

Thanks and Regards

Altaf Nizamuddin

Hi Altaf,

It is possible to design reports in Access, and you can import it with BIDS with some restrictions. Well, i never tried, but if you can import the report viewer control in Access and you write a custom code behind, then you should be able to render the report. Again, I never tried it, just an idea.

Regards,

Janos

ps.: maybe I'll try it

|||http://www.microsoft.com/technet/prodtechnol/sql/2000/deploy/migratereports.mspx|||

Hi Adolf,

Thanks a lot but it will never work in my sceneraio,

The article explains "How to Migrate Access reports to reporting services", but i want to run Reporting service in MS-Access environment, I mean to say i have to use MS-Access as user interface to design and generate report (instead of Visual studio IDE) and the Sql server 2005 should be Report Server.

Thanks and Regards

Altaf Nizamuddin

|||So just design it in Access and migrate it.

Personally I'd just take the hit on learning how to create reports in RS.sql

How to restore the entire replication topology in different boxe

We are migrating the entire sqlserver environment from Window2000 to Windows
2003 on different boxes with different NT servernames. I have installed the
sqlserver instances and I have restored the publisher, distribution db on the
primary side and the subscriber db on the replicated side. However, I don't
see any publications under the replication folder. Do I need to go through
the replication configuration first then restore the distribution?
Please advise. Thanks.
Wen,
for migrating to another server which has a different netbios name, the only
realistic solution is to script out the publications on the original setup,
install the new servers and then run the scripts on the new server, changing
the necessary parts eg servername and job owners.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)