Re: Exporting/Editing Risks

I do have a basic SQL and VBA knowledge; however, I work in a large
corporation where everything like that would have to go through the IT
department with a Service Request, which may take a while...

"Rod Gill" wrote:

> Hi,
>
> I've done this, but it needs VBA code.
>
> 1) In SQL Server create a read only userID for the macro to use to read
> data. Add it to the Project database and the WSS database.
> 2) Create a view in the Project database that shows all risks and includes
> names of assigned to people etc.
> 3) in any version of Excel read the view into a ***. You can add a drop
> down list to pre-select projects, or whatever you want.
>
> Over a slowwww wide area Network (WAN) I've had 100 records pull down into
> Excel within 3-5 seconds. In fact I've created Excel macros that at a click
> of a button download a lot of standard and custom information from Project
> Server and creates 80% of the week's report at the click of a button.
>
> If you have moderate knowledge of SQL Server and reasonable VBA skills it's
> relatively straightforward to do.
>
> --
>
> Rod Gill
> Project MVP
>
>
> "Kristi F" <KristiF@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
> news:592395B5-EC4E-42FD-87F7-B79621936F84@xxxxxxxxxxxxxxxx
> >I am trying to use the Risks in Web Access 2003, and although I like the
> > on-line containment of these risks, it is often necessary to export this
> > information to Excel in order to manipulate the information and report on
> > it.
> > However, when I hit 'Export to Spread***', I get a message about Windows
> > Sharepoint services...does this mean that I have to have Excel 2003
> > intalled
> > in order to use this functionality? Is there another way to get all the
> > risk
> > information into a spread***?
> >
> > Thanks
>
>
>
.