Hi Thomas,
Thanks for your response.
Actually I didn't change any setting for any dataset. All the settings are still like how they were
set by loading the dump-files. However, I checked the entity control for all the dataset entities of
the RYCSO dataset. The dataset that should deploy my generated objects. The dataset has 13 entities.
2 of them (GSMVP and RYMDV) actually didn't have 'deploy data' and 'version data' checked on. I
started from scratch all over again with the 2 fields checked fot both entities and again deployed.
But there are no differences.
If in the 'dataset export' tool I select dataset RYCSO and go to the 'record list', I can select all
the objects I want by filtering them. But that's exactly what I don't want. I just want to check the
'deploy all modified data' checkbox and let the export-tool determine what data has been changed.
Could it be the case, that because the data I want to deploy, is completely new to Dynamics, there
is no data version available for it? If so, any ideas on how or when that data version is created?
TIA
Johan B.
- Original Message -
From: "Thomas D. Barringer" To: "Johan Beumer" Sent: Tuesday, 25 March, 2003 16:52
Subject: Re: Deployment
Hi Johan,
I haven't seen another message on this go by so I'll take a quick shot at this even though I haven't
used it in a few months.
Have you verified that the "version data" and "deploy data" toggles are turned on in the entity
control of the relevant tables? These flags must also be turned on in the Deployment Dataset
Definition screen for the datasets including these tables.
The "version data" flag in particular must be on for change control records to be updated; turning
off the "deploy data" flag permits you to exclude certain data from the ado (if I remember
correctly.) So the flags must be on in both places -- the "versiond data" flag is examined when the
record is updated, the "deploy data" flag is examined when the ado is generated.
Hope this helps.
--
Tom Barringer A "rogue state" is a country which
Staff Consultant acts unilaterally and violently.
Empowerment Center NA Which part of this definition
Progress Software does not apply to America today?
Original message:
Hi there,
I'm struggling with some problems/questions on deploying. I did the =
following :
- created a new empty ICF-database, loaded df-, dump- and sequence-file;
- set site number;
- created product and module;
- entity import
- generated objects
So far, nothing new or different from what is descibed in the document =
'getting started with Progress Dynamics' chapter 2, till paragraph =
2.1.9.
If at this point I start a deploy and check 'deploy all modified data', =
it leaves me with 1 subset for dataset GSCPR and 1 for GSCEM. For every =
field of an entity mnemonic it creates an empty ado-file, just like for =
the generated dynamic-viewer and the dynamics-browser.
If at this point I import these datasets into another empty database, I =
don't have any objects, although they had been generated.
Can anyone tell me if I am doing something wrong or what to do to get =
the generated objects deployed?
I'm using latest V3.0 (Baseline 2) code downloaded with wincvs and 91D =
patch 5.
TIA,
Johan B.
Caesar Vitalogic
To unsubscribe, e-mail: dev-unsubscribe@icf.possenet.org
For additional commands, e-mail: dev-help@icf.possenet.org
I am trying to re-install on a laptop running WinXP
Home version. I am running Progress 9.1D05 with a
fresh d/l of POSSE code today. When I try to execute
pbuild, I get errors relating to path problems. I
have narrowed it down to the following command in
pbuild:
POSSE="`cygpath -pwa \"$POSSE\"`"
If I go to a cygwin shell and do:
echo $POSSE
it correctly returns C:\Possework\PosseDynamics
If I then type in the command above and then do echo
$POSSE, it returns:
C;c:\Possework\PosseDynamics
It has now stuck a "C;" on the front. Since many of
the other env vars are built from this, most of them
are now wrong with the "C;" on the front.
Anybody seen this before? Anybody know how to fix it?
Rick
=====
Rick Terrell
__________________________________________________
Do you Yahoo!?
Yahoo! Platinum - Watch CBS' NCAA March Madness, live on your desktop!
http://platinum.yahoo.com
To unsubscribe, e-mail: dev-unsubscribe@icf.possenet.org
For additional commands, e-mail: dev-help@icf.possenet.org
Hi Rick,
This is a problem with the way the cygpath function behaves in winXP.
It used to interpret the c: in the environment variable as part of the
path. Now it mistakes it for a path delimiter and replaces the colon
with a semi colon. I have also run into this using pbuild on a winXP
machine.
You need to do a couple of things. First there is a section several
lines down that defines what the TEMPDIR directory setting is. You'll
need to manually change this to a hard-coded value so that it no longer
uses the environment variable. There are two, make sure you get the one
for cygwin.
Second, you'll need to change all the commands (I think there are four)
that look like your line below
POSSE="`cygpath -pwa ..."
Change the lines to change the switches passed to the cygpath variable
to -wa (remove the p) so that it reads
POSSE="`cygpath -pa ..."
Hope this helps.
mattB
Rick Terrell wrote:
>I am trying to re-install on a laptop running WinXP
>Home version. I am running Progress 9.1D05 with a
>fresh d/l of POSSE code today. When I try to execute
>pbuild, I get errors relating to path problems. I
>have narrowed it down to the following command in
>pbuild:
>
POSSE="`cygpath -pwa \"$POSSE\"`"
>
>If I go to a cygwin shell and do:
echo $POSSE
>it correctly returns C:\Possework\PosseDynamics
>
>If I then type in the command above and then do echo
>$POSSE, it returns:
>
>C;c:\Possework\PosseDynamics
>
>It has now stuck a "C;" on the front. Since many of
>the other env vars are built from this, most of them
>are now wrong with the "C;" on the front.
>
>Anybody seen this before? Anybody know how to fix it?
>
>Rick
>
>
>
>=====
>Rick Terrell
>
>__________________________________________________
>Do you Yahoo!?
>Yahoo! Platinum - Watch CBS' NCAA March Madness, live on your desktop!
>http://platinum.yahoo.com
>
>
>To unsubscribe, e-mail: dev-unsubscribe@icf.possenet.org
>For additional commands, e-mail: dev-help@icf.possenet.org
>
>
>
To unsubscribe, e-mail: dev-unsubscribe@icf.possenet.org
For additional commands, e-mail: dev-help@icf.possenet.org