H
Hari Prasadh
Hi,
Not related to PPT (its about how to MANAGE huge PPT projects) as such but
didnt know where else to post.
I have to automate a huge series of PPT reports like X number of Class 1
kind of reports having lets say Y slides and then Z number of Class 2 kind
of reports having lets say W slides each and Class 3, Class 4 and so on and
on.
The numbers X, Y, Z, W and so on and on are quite considerable.
a. Within a particular class like lets say Class1 the structure (layout and
kind/type of objects) of slides (INTRA class comparison - Slide 1 of PPT1 =
Slide1 of PPT2 , Slide2 of PPT1 = Slide2 of PPT2 and so on) would be 85-90%
SAME.
b. Some of the reports within Class 1 might have some EXTRA slides in the
middle of the presentation. Like if there are 100 slides in PPT1 there might
be 110 in PPT2 so Slide1 to Slide 73 of PPT1 would be equal in layout to
Slide 1 to slide 73 of PPT2, but Slide 74 is an extra slide in PPT2. So,
Slide 74 in PPT1 would be equal to Slide 75 of PPT2 and the pattern would
continue with intermittent addition of slides in either of PPT1 or PPT2.
c. Having said that within a particular PPT, Slide1 layout/objects is not
equal to Slide2 layout/objects and so on.
d All the data resides in Excel (TONS of Excel files I believe) and it
would have to be pasted in PPT in OLE -- editable -- form (as a Excel
sheet/Chart/MS Applet Graph).
There will be a series of different macro calls with changes in parameter
(Considering the quantum of project, parameter passing itself is one big
headache and a good candidate for effective PM aka Parameter Management).
I have pondered a little on how I will be executing it. One stuff I thought
of is that since I would be running macros on different computers and
different computers will have different Paths for storing Input Excel data
so I needed to give user (user is myself - would be running the macros
parallely in many computers) the ability to change path (Hard-coded paths
wont work). Also, standard input boxes for changing paths wont work because
considering the number of objects in which data is to be populated user cant
keep on writing/specifying paths during macro execution. So, I split up
path names in to one Soft-path and second Hard-path and stored both of them
in an excel sheet.
Soft-path is something like - C:\Documents and Settings\Hari\Project Name\ -
This part of the path is same for all objects in all slides within all CLASS
of reports.
Hard-path for a specific object's data folder - Class1\MRAUTE1\2005\ -- The
Hard path will change depending on the object, class and year. (I have give
unique names to each object and created separate folders for them like
MRAUTE1 above.)
So, if we move to a different computer then I would have to change only the
soft-path (a single cell in a global excel file has to be changed and it
will adjust paths for all objects). Again when we move to a different
computer I would paste my data in such a way that it matches the folder
structure as specified in the hard path of my excel file.
New computer:-
Soft-path:- C:\Documents and Settings\Incognito\Project Name\
Hard-Path: - Class1\MRAUTE1\2005\
My boss suggested that for better project mgmt it would be helpful if I
create different folders for different slides within each class of report.
So, the present hard-path could be changed to Class1\Slide1\MRAUTE1\2005\
for an object named MRAUTE1 within Slide1 of Class1 report and again for
object named YUERTW1 in Slide2 of Class1 it would be like
Class1\Slide2\YUERTW1\2005\ and so on and on.
Initially I thought that it would be a great idea as it would have been
broken in to manageable chunks. But.... in light of point b) above it causes
some NEW problems. As mentioned slide1 to slide 73 are equal within a
particular class of reports, but slide 74 might be different in some PPT's
within that Class and same for future slides.
So, when am passing parameters I would get in to deep problems. Say I
instruct my macro -- Go and fetch data for object named as "PRAEED42" in
slide 74 for PPT1 in Class1 from the Hard-path--
Class1\Slide74\PRAEED42\2005\. But slide 74 for PPT2 in Class1 there might
be no object named "PRAEED42". On the other hand it is in slide 75 of PPT2
we find an object named PRAEED42" (slide 75 of PPT2 is equivalent to slide
74 of PPT1).
In all if I make different folders for different slides Project mgmt might
seem to be better but parameter management would become EVEN more tedious.
Any thoughts?
Would be grateful if I could get some guidelines/ideas on how to MANAGE
(strategic/tactical) things specifically in PPT automation.
Thanks a lot,
Hari
India
Not related to PPT (its about how to MANAGE huge PPT projects) as such but
didnt know where else to post.
I have to automate a huge series of PPT reports like X number of Class 1
kind of reports having lets say Y slides and then Z number of Class 2 kind
of reports having lets say W slides each and Class 3, Class 4 and so on and
on.
The numbers X, Y, Z, W and so on and on are quite considerable.
a. Within a particular class like lets say Class1 the structure (layout and
kind/type of objects) of slides (INTRA class comparison - Slide 1 of PPT1 =
Slide1 of PPT2 , Slide2 of PPT1 = Slide2 of PPT2 and so on) would be 85-90%
SAME.
b. Some of the reports within Class 1 might have some EXTRA slides in the
middle of the presentation. Like if there are 100 slides in PPT1 there might
be 110 in PPT2 so Slide1 to Slide 73 of PPT1 would be equal in layout to
Slide 1 to slide 73 of PPT2, but Slide 74 is an extra slide in PPT2. So,
Slide 74 in PPT1 would be equal to Slide 75 of PPT2 and the pattern would
continue with intermittent addition of slides in either of PPT1 or PPT2.
c. Having said that within a particular PPT, Slide1 layout/objects is not
equal to Slide2 layout/objects and so on.
d All the data resides in Excel (TONS of Excel files I believe) and it
would have to be pasted in PPT in OLE -- editable -- form (as a Excel
sheet/Chart/MS Applet Graph).
There will be a series of different macro calls with changes in parameter
(Considering the quantum of project, parameter passing itself is one big
headache and a good candidate for effective PM aka Parameter Management).
I have pondered a little on how I will be executing it. One stuff I thought
of is that since I would be running macros on different computers and
different computers will have different Paths for storing Input Excel data
so I needed to give user (user is myself - would be running the macros
parallely in many computers) the ability to change path (Hard-coded paths
wont work). Also, standard input boxes for changing paths wont work because
considering the number of objects in which data is to be populated user cant
keep on writing/specifying paths during macro execution. So, I split up
path names in to one Soft-path and second Hard-path and stored both of them
in an excel sheet.
Soft-path is something like - C:\Documents and Settings\Hari\Project Name\ -
This part of the path is same for all objects in all slides within all CLASS
of reports.
Hard-path for a specific object's data folder - Class1\MRAUTE1\2005\ -- The
Hard path will change depending on the object, class and year. (I have give
unique names to each object and created separate folders for them like
MRAUTE1 above.)
So, if we move to a different computer then I would have to change only the
soft-path (a single cell in a global excel file has to be changed and it
will adjust paths for all objects). Again when we move to a different
computer I would paste my data in such a way that it matches the folder
structure as specified in the hard path of my excel file.
New computer:-
Soft-path:- C:\Documents and Settings\Incognito\Project Name\
Hard-Path: - Class1\MRAUTE1\2005\
My boss suggested that for better project mgmt it would be helpful if I
create different folders for different slides within each class of report.
So, the present hard-path could be changed to Class1\Slide1\MRAUTE1\2005\
for an object named MRAUTE1 within Slide1 of Class1 report and again for
object named YUERTW1 in Slide2 of Class1 it would be like
Class1\Slide2\YUERTW1\2005\ and so on and on.
Initially I thought that it would be a great idea as it would have been
broken in to manageable chunks. But.... in light of point b) above it causes
some NEW problems. As mentioned slide1 to slide 73 are equal within a
particular class of reports, but slide 74 might be different in some PPT's
within that Class and same for future slides.
So, when am passing parameters I would get in to deep problems. Say I
instruct my macro -- Go and fetch data for object named as "PRAEED42" in
slide 74 for PPT1 in Class1 from the Hard-path--
Class1\Slide74\PRAEED42\2005\. But slide 74 for PPT2 in Class1 there might
be no object named "PRAEED42". On the other hand it is in slide 75 of PPT2
we find an object named PRAEED42" (slide 75 of PPT2 is equivalent to slide
74 of PPT1).
In all if I make different folders for different slides Project mgmt might
seem to be better but parameter management would become EVEN more tedious.
Any thoughts?
Would be grateful if I could get some guidelines/ideas on how to MANAGE
(strategic/tactical) things specifically in PPT automation.
Thanks a lot,
Hari
India