From: Rob Schneider on
When you say "last ones in the logic", does this mean they are the last
tasks in the network model of the project? If this is the case, then my
hunch is you will have some trouble as you should *want* the last tasks
on the model in Project to move (be unconstrained)in response to changes
upstream (slow progress, faster-than-anticipated progress, changes, etc.).

You use the deadline field to allow Project to detect and report for you
when these completion dates are outwith the project plans for expected
completion.

I'm just guessing based on what you say, though. If you haven't taken a
look at how the deadline feature works in Project, take a look.


--rms

www.rmschneider.com




On 13/04/10 06:40, Luc Overdulve wrote:
> On 12 apr, 23:35, Jim Aksel<JimAk...(a)discussions.microsoft.com>
> wrote:
>> However, something scares me.
>>
>> These constraint types are quite literal. If it is "Must Start On" .... it
>> means (to Project) ... "I don't care what the schedule logic says, this task
>> Must Start On this date so I will make it so.
>>
>
> Thank you for answering and your suggestion!
>
> These constraints are the last ones in the logic, so no real harmful
> things are going to happen.
> But thanks for you advise!
>
> Luc
From: Rod Gill on
Well the good news is that VBA is many times more productive than that. I've
just had to write a Project Add-in using C#. Just converting from VBA was a
real pain, Case sensitive, idiosyncratic syntax, ongoing cryptic error
messages for Africa and more!

Links and saving to a network location over a dodgy network are the main
culprits for file corruption.

My alternative uses a separate store for milestone data, saved by a macro in
the source project and read by another macro in the consuming project. The
store can be a text or Excel file, or of course a database such as SQL
Server or Access.

--

Rod Gill
Microsoft MVP for Project - http://www.project-systems.co.nz

Author of the only book on Project VBA, see: http://www.projectvbabook.com




"Luc Overdulve" <l.overdulve(a)gw.rotterdam.nl> wrote in message
news:d71402e0-62ac-469d-ac26-4cc197fbde3d(a)u22g2000yqf.googlegroups.com...
> On 12 apr, 23:00, "Rod Gill" <rodATproject-systemsDOTcoDOTnz> wrote:
>
>>
>> My personal solution is to use VBA to read milestone dates from files and
>> to
>> create snapshot master files each week (no link). This eliminates all
>> links
>> and corruption risk.
>>
>
> I know that I have to be very careful with this, but you are scaring
> me using the word 'corruption'. I met some corrupted files before...
>
> So, I am very interested in your alternative. But I am sorry, I am not
> a VBA specialist.
>
> In the eighties I used to build our own planning application on
> mainframe and later on for TOS and MS DOS running systems, but all
> using Fortran77 and a very little bit of C++.
>
> Luc
>
>
> __________ Information from ESET Smart Security, version of virus
> signature database 5024 (20100413) __________
>
> The message was checked by ESET Smart Security.
>
> http://www.eset.com
>
>
>

__________ Information from ESET Smart Security, version of virus signature database 5024 (20100413) __________

The message was checked by ESET Smart Security.

http://www.eset.com