Project 2003

[ellitech]

We have a user who pulls information from an ERP database and puts it into
Project 2003 when she generates a report or a schedule. It will put in
several columns of information that she does not require when she prints it
out. How can she delete out the columns that she doesn't need and create a
template from that view that could be reused everytime she needs to print it
out?

 

[ahelp]

A view consists of a table, group, screen, and filter.
1. Go to View menu, Table, More Tables, select a table that's close, and Copy
2. Modify columns as necessary, rename, & OK
3. Go to View, More Views, New, OK for Single view, & choose your options

Now after the ERP import she can apply the new view & print out the info

 

[ellitech]

Hi Mike,

Thanks for the response back, however I am not familiar with Project 2003
and as such I am unable to determine what type of table is presently being
displayed as well as the appropiate table, group, screen, and filter. Is
there a way that I can go in and determine what type of table the ERP is
displaying into when it imports the data into Project 2003?

I appreciate you taking the time to help out with this matter as this is a
cause of annoyance for the user.

Michael

 

[ahelp]

Hi Michael,
Under the View menu, there will be a check mark next to the name of the
current view. Lower on the menu, it will say Table, along with the name of
the current table. The table defines which columns (fields) you see, and
consequently, which ones will print out. The ERP report will probably use
whatever the current view/table is, so if what you see is not what you want,
you can change it. Though it looks like Excel, it's not. If you delete a
column, the data is still there, you're simply not looking at it. If you
don't want to mess with creating a new view, you can also add/delete columns
(fields) by right-clicking in the column header. The problem with doing it
this way is that the next time you open Project, it will go back to the
default view and columns. So if there's a view you'll use repeatedly, it's
best to define/create it.
If you're going to be working with Project much, I'd suggest getting a good
book, as it's not as intuitive as Word or Excel. Dynamic Scheduling with MS
Project 2003 by Uyttewaal (published by IIL) is pretty in depth.