Re: Ole Automation of Project 2000
From: JackD (momokuri_at_gmail)
Date: 09/24/04
- Next message: JackD: "Re: MSProject.Application.FileSaveAs"
- Previous message: JackD: "Re: MS Project 2000, Assignments"
- In reply to: Dan Roy: "Ole Automation of Project 2000"
- Messages sorted by: [ date ] [ thread ]
Date: Fri, 24 Sep 2004 14:02:23 -0700
The usual statement in project VBA is something like this:
for each task in activeproject.tasks
if not task is nothing then
'do something
end if
next task
If you don't want to do that you can filter by task name and then select all
and use the activeselection.tasks collection to iterate through.
-Jack
"Dan Roy" <Dan Roy@discussions.microsoft.com> wrote in message
news:76D6DFC9-DE5D-49EA-9C30-0462CE3B7601@microsoft.com...
> I have developed an application which uses automation with both MS Project
> 2000 and Excel. I am able to read/write data to almost every field in
> Project and read/save data to Excel for analysis.
>
> On eof the few remaining problems which i would like to address is reading
a
> blank line in Project. Reading a blank line causes my application to
raise
> an exception but I have not been able to track down the source of the
> exception, yet. I have experimented with the windows function VarIsEmpty,
> specifically meant to detect un-initialized OleVariants. My application
uses
> a typelib based on the MSProject.olb type library, so I have access to all
of
> those fields and functions.
>
> Are there any fields in the OLB object model which will help me to
> distinguish a blank line from a task.id which contains task data.
>
> I am using Borland Delphi V6 Enterprise in an MS Windows 2000 environment.
- Next message: JackD: "Re: MSProject.Application.FileSaveAs"
- Previous message: JackD: "Re: MS Project 2000, Assignments"
- In reply to: Dan Roy: "Ole Automation of Project 2000"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
