PDA

View Full Version : Where are the column settings



Jim Albright
3-Oct-2008, 03:57 PM
In the previous dbbldg, we could go to the tab page marked "column settings". There we could add
settings like capslock, key field, default values, lookups, and masks.

I don't see this functionality in the studio, and it has been removed from the new ddbldr.


Jim Albright
Novell CNE
President
Wizard Systems, Inc.
http://home.cfl.rr.com/wizardsystems

Sonny Falk
3-Oct-2008, 04:42 PM
> In the previous dbbldg, we could go to the tab page marked "column
> settings". There we could add settings like capslock, key field, default
> values, lookups, and masks.
>
> I don't see this functionality in the studio, and it has been removed from
> the new ddbldr.

The column settings you're asking about are actually DD class settings, not
table settings. So they're available in the DD designer, not in the Table
Editor.

You can open a DD in the designer in several different ways, from Workspace
Explorer -> Data Dictionaries and double-click the DD you want to open. Or
you can open it from Table Explorer by finding the associated table and open
up the treeview node labeled Data Dictionaries and double click the DD from
there. Or you can open the DD from File -> Open File and browse to the DD,
or any other means of opening source files. In any case, when you open the
DD, it will now open in the DD designer as well as in the source code
editor, just like when you open a view/dialog for example.

-Sonny

Jim Albright
7-Oct-2008, 09:37 AM
Sonny,

When I do as you instructed, I get the DD source file opened. But I can't find the DD designer. When
in the DD source I right click on the source, and select "switch to designer" I get the "No Objects
to Model" page.

Help,

Jim

"Sonny Falk" <sonny-f@dataaccess.com> wrote in message
news:jkrlqDaJJHA.3324@dacmail.dataaccess.com...
>> In the previous dbbldg, we could go to the tab page marked "column settings". There we could add
>> settings like capslock, key field, default values, lookups, and masks.
>>
>> I don't see this functionality in the studio, and it has been removed from the new ddbldr.
>
> The column settings you're asking about are actually DD class settings, not table settings. So
> they're available in the DD designer, not in the Table Editor.
>
> You can open a DD in the designer in several different ways, from Workspace Explorer -> Data
> Dictionaries and double-click the DD you want to open. Or you can open it from Table Explorer by
> finding the associated table and open up the treeview node labeled Data Dictionaries and double
> click the DD from there. Or you can open the DD from File -> Open File and browse to the DD, or
> any other means of opening source files. In any case, when you open the DD, it will now open in
> the DD designer as well as in the source code editor, just like when you open a view/dialog for
> example.
>
> -Sonny
>

Jim Albright
7-Oct-2008, 09:42 AM
Sonny,

I forgot to mention that in the "Output" view, I get a message that says, "Could not parse the Data
Dictionary source file "APCICTRL.DD". This file may be an old style DD.
I was under the impress that the old style DD would be converted automatically when I migrated.

Jim

"Sonny Falk" <sonny-f@dataaccess.com> wrote in message
news:jkrlqDaJJHA.3324@dacmail.dataaccess.com...
>> In the previous dbbldg, we could go to the tab page marked "column settings". There we could add
>> settings like capslock, key field, default values, lookups, and masks.
>>
>> I don't see this functionality in the studio, and it has been removed from the new ddbldr.
>
> The column settings you're asking about are actually DD class settings, not table settings. So
> they're available in the DD designer, not in the Table Editor.
>
> You can open a DD in the designer in several different ways, from Workspace Explorer -> Data
> Dictionaries and double-click the DD you want to open. Or you can open it from Table Explorer by
> finding the associated table and open up the treeview node labeled Data Dictionaries and double
> click the DD from there. Or you can open the DD from File -> Open File and browse to the DD, or
> any other means of opening source files. In any case, when you open the DD, it will now open in
> the DD designer as well as in the source code editor, just like when you open a view/dialog for
> example.
>
> -Sonny
>

Stephen W. Meeley
7-Oct-2008, 09:55 AM
Hi Jim,

All the data dictionaries that are used in any project in the source
workspace should have been updated by the migration, and there should be a
..bak file for all the updated files in the DDSrc folder. Can you verify that
APCICTRL.DD is used in at least one of the projects in the workspace that
you migrated? Also, can you please see if the .bak file exists (and if so,
send us a copy of the .dd and the .bak file)?

Best regards,

-SWM-


"Jim Albright" <jalbright@cfl.rr.com> wrote in message
news:PHK6HsIKJHA.1636@dacmail.dataaccess.com...
> Sonny,
>
> I forgot to mention that in the "Output" view, I get a message that says,
> "Could not parse the Data Dictionary source file "APCICTRL.DD". This file
> may be an old style DD.
> I was under the impress that the old style DD would be converted
> automatically when I migrated.
>
> Jim
>
> "Sonny Falk" <sonny-f@dataaccess.com> wrote in message
> news:jkrlqDaJJHA.3324@dacmail.dataaccess.com...
>>> In the previous dbbldg, we could go to the tab page marked "column
>>> settings". There we could add settings like capslock, key field, default
>>> values, lookups, and masks.
>>>
>>> I don't see this functionality in the studio, and it has been removed
>>> from the new ddbldr.
>>
>> The column settings you're asking about are actually DD class settings,
>> not table settings. So they're available in the DD designer, not in the
>> Table Editor.
>>
>> You can open a DD in the designer in several different ways, from
>> Workspace Explorer -> Data Dictionaries and double-click the DD you want
>> to open. Or you can open it from Table Explorer by finding the associated
>> table and open up the treeview node labeled Data Dictionaries and double
>> click the DD from there. Or you can open the DD from File -> Open File
>> and browse to the DD, or any other means of opening source files. In any
>> case, when you open the DD, it will now open in the DD designer as well
>> as in the source code editor, just like when you open a view/dialog for
>> example.
>>
>> -Sonny
>>
>
>

Jim Albright
7-Oct-2008, 10:52 AM
Stephen,

I went back and:
1. uninstalled Alpha 1 (using Windows Control Panel add/remove...)
2. removed the registry entries (Hkey_LM and Hkey_CU)
3. deleted the new project folder.

Then I reinstalled Alpha 1.
I Opened the current 14.0 project in the new 14.1 studio, and migrated again.
Same result-- the DD files (in a brand new folder i.e. DD2008) were not changed.
There are no backup files (other than old ones from 14.0, BTW these got copied too), and the .DD
files all had the same date/time stamp as the 14.0 DD_SRC folder.

The migration did parse all the .src files for DD items. But that was it.

APCICTRL is a control/system file used in all the .src in this project. Confirmed.
All 245 .DD files are unchanged! The Migration program appears to have simply copied the .DD's .FD's
and .BAK's from the old DD folder.

Since I have done this twice, I am either doing something wrong each time or this is not working as
designed.

Jim


"Stephen W. Meeley" <stephen-m@dataaccess.com> wrote in message
news:Qm2PIzIKJHA.4840@dacmail.dataaccess.com...
> Hi Jim,
>
> All the data dictionaries that are used in any project in the source workspace should have been
> updated by the migration, and there should be a .bak file for all the updated files in the DDSrc
> folder. Can you verify that APCICTRL.DD is used in at least one of the projects in the workspace
> that you migrated? Also, can you please see if the .bak file exists (and if so, send us a copy of
> the .dd and the .bak file)?
>
> Best regards,
>
> -SWM-
>
>
> "Jim Albright" <jalbright@cfl.rr.com> wrote in message
> news:PHK6HsIKJHA.1636@dacmail.dataaccess.com...
>> Sonny,
>>
>> I forgot to mention that in the "Output" view, I get a message that says, "Could not parse the
>> Data Dictionary source file "APCICTRL.DD". This file may be an old style DD.
>> I was under the impress that the old style DD would be converted automatically when I migrated.
>>
>> Jim
>>
>> "Sonny Falk" <sonny-f@dataaccess.com> wrote in message
>> news:jkrlqDaJJHA.3324@dacmail.dataaccess.com...
>>>> In the previous dbbldg, we could go to the tab page marked "column settings". There we could
>>>> add settings like capslock, key field, default values, lookups, and masks.
>>>>
>>>> I don't see this functionality in the studio, and it has been removed from the new ddbldr.
>>>
>>> The column settings you're asking about are actually DD class settings, not table settings. So
>>> they're available in the DD designer, not in the Table Editor.
>>>
>>> You can open a DD in the designer in several different ways, from Workspace Explorer -> Data
>>> Dictionaries and double-click the DD you want to open. Or you can open it from Table Explorer by
>>> finding the associated table and open up the treeview node labeled Data Dictionaries and double
>>> click the DD from there. Or you can open the DD from File -> Open File and browse to the DD, or
>>> any other means of opening source files. In any case, when you open the DD, it will now open in
>>> the DD designer as well as in the source code editor, just like when you open a view/dialog for
>>> example.
>>>
>>> -Sonny
>>>
>>
>>
>
>

Stephen W. Meeley
7-Oct-2008, 10:59 AM
Hi Jim,

We'll figure it out. Can you send me copies of your .sws and .ws files (both
the 14.0 and the 14.1 migrated versions) so I can understand your structure?
Thanks.

Also, in the 14.0 workspace, does everything model correctly? Do you have
any warnings in the Problem Resolution panel?

Best regards,

-SWM-

"Jim Albright" <jalbright@cfl.rr.com> wrote in message
news:zUssdTJKJHA.7988@dacmail.dataaccess.com...
> Stephen,
>
> I went back and:
> 1. uninstalled Alpha 1 (using Windows Control Panel add/remove...)
> 2. removed the registry entries (Hkey_LM and Hkey_CU)
> 3. deleted the new project folder.
>
> Then I reinstalled Alpha 1.
> I Opened the current 14.0 project in the new 14.1 studio, and migrated
> again.
> Same result-- the DD files (in a brand new folder i.e. DD2008) were not
> changed.
> There are no backup files (other than old ones from 14.0, BTW these got
> copied too), and the .DD files all had the same date/time stamp as the
> 14.0 DD_SRC folder.
>
> The migration did parse all the .src files for DD items. But that was it.
>
> APCICTRL is a control/system file used in all the .src in this project.
> Confirmed.
> All 245 .DD files are unchanged! The Migration program appears to have
> simply copied the .DD's .FD's and .BAK's from the old DD folder.
>
> Since I have done this twice, I am either doing something wrong each time
> or this is not working as designed.
>
> Jim
>
>
> "Stephen W. Meeley" <stephen-m@dataaccess.com> wrote in message
> news:Qm2PIzIKJHA.4840@dacmail.dataaccess.com...
>> Hi Jim,
>>
>> All the data dictionaries that are used in any project in the source
>> workspace should have been updated by the migration, and there should be
>> a .bak file for all the updated files in the DDSrc folder. Can you verify
>> that APCICTRL.DD is used in at least one of the projects in the workspace
>> that you migrated? Also, can you please see if the .bak file exists (and
>> if so, send us a copy of the .dd and the .bak file)?
>>
>> Best regards,
>>
>> -SWM-
>>
>>
>> "Jim Albright" <jalbright@cfl.rr.com> wrote in message
>> news:PHK6HsIKJHA.1636@dacmail.dataaccess.com...
>>> Sonny,
>>>
>>> I forgot to mention that in the "Output" view, I get a message that
>>> says, "Could not parse the Data Dictionary source file "APCICTRL.DD".
>>> This file may be an old style DD.
>>> I was under the impress that the old style DD would be converted
>>> automatically when I migrated.
>>>
>>> Jim
>>>
>>> "Sonny Falk" <sonny-f@dataaccess.com> wrote in message
>>> news:jkrlqDaJJHA.3324@dacmail.dataaccess.com...
>>>>> In the previous dbbldg, we could go to the tab page marked "column
>>>>> settings". There we could add settings like capslock, key field,
>>>>> default values, lookups, and masks.
>>>>>
>>>>> I don't see this functionality in the studio, and it has been removed
>>>>> from the new ddbldr.
>>>>
>>>> The column settings you're asking about are actually DD class settings,
>>>> not table settings. So they're available in the DD designer, not in the
>>>> Table Editor.
>>>>
>>>> You can open a DD in the designer in several different ways, from
>>>> Workspace Explorer -> Data Dictionaries and double-click the DD you
>>>> want to open. Or you can open it from Table Explorer by finding the
>>>> associated table and open up the treeview node labeled Data
>>>> Dictionaries and double click the DD from there. Or you can open the DD
>>>> from File -> Open File and browse to the DD, or any other means of
>>>> opening source files. In any case, when you open the DD, it will now
>>>> open in the DD designer as well as in the source code editor, just like
>>>> when you open a view/dialog for example.
>>>>
>>>> -Sonny
>>>>
>>>
>>>
>>
>>
>
>

John van Houten
7-Oct-2008, 11:47 AM
Also usefull would be the DDClassList.xml file. It is possible that your .DD
files are not registered in this list?

regards John van Houten


"Stephen W. Meeley" <stephen-m@dataaccess.com> wrote in message
news:YYIw1WJKJHA.1980@dacmail.dataaccess.com...
> Hi Jim,
>
> We'll figure it out. Can you send me copies of your .sws and .ws files
> (both the 14.0 and the 14.1 migrated versions) so I can understand your
> structure? Thanks.
>
> Also, in the 14.0 workspace, does everything model correctly? Do you have
> any warnings in the Problem Resolution panel?
>
> Best regards,
>
> -SWM-
>
> "Jim Albright" <jalbright@cfl.rr.com> wrote in message
> news:zUssdTJKJHA.7988@dacmail.dataaccess.com...
>> Stephen,
>>
>> I went back and:
>> 1. uninstalled Alpha 1 (using Windows Control Panel add/remove...)
>> 2. removed the registry entries (Hkey_LM and Hkey_CU)
>> 3. deleted the new project folder.
>>
>> Then I reinstalled Alpha 1.
>> I Opened the current 14.0 project in the new 14.1 studio, and migrated
>> again.
>> Same result-- the DD files (in a brand new folder i.e. DD2008) were not
>> changed.
>> There are no backup files (other than old ones from 14.0, BTW these got
>> copied too), and the .DD files all had the same date/time stamp as the
>> 14.0 DD_SRC folder.
>>
>> The migration did parse all the .src files for DD items. But that was it.
>>
>> APCICTRL is a control/system file used in all the .src in this project.
>> Confirmed.
>> All 245 .DD files are unchanged! The Migration program appears to have
>> simply copied the .DD's .FD's and .BAK's from the old DD folder.
>>
>> Since I have done this twice, I am either doing something wrong each time
>> or this is not working as designed.
>>
>> Jim
>>
>>
>> "Stephen W. Meeley" <stephen-m@dataaccess.com> wrote in message
>> news:Qm2PIzIKJHA.4840@dacmail.dataaccess.com...
>>> Hi Jim,
>>>
>>> All the data dictionaries that are used in any project in the source
>>> workspace should have been updated by the migration, and there should be
>>> a .bak file for all the updated files in the DDSrc folder. Can you
>>> verify that APCICTRL.DD is used in at least one of the projects in the
>>> workspace that you migrated? Also, can you please see if the .bak file
>>> exists (and if so, send us a copy of the .dd and the .bak file)?
>>>
>>> Best regards,
>>>
>>> -SWM-
>>>
>>>
>>> "Jim Albright" <jalbright@cfl.rr.com> wrote in message
>>> news:PHK6HsIKJHA.1636@dacmail.dataaccess.com...
>>>> Sonny,
>>>>
>>>> I forgot to mention that in the "Output" view, I get a message that
>>>> says, "Could not parse the Data Dictionary source file "APCICTRL.DD".
>>>> This file may be an old style DD.
>>>> I was under the impress that the old style DD would be converted
>>>> automatically when I migrated.
>>>>
>>>> Jim
>>>>
>>>> "Sonny Falk" <sonny-f@dataaccess.com> wrote in message
>>>> news:jkrlqDaJJHA.3324@dacmail.dataaccess.com...
>>>>>> In the previous dbbldg, we could go to the tab page marked "column
>>>>>> settings". There we could add settings like capslock, key field,
>>>>>> default values, lookups, and masks.
>>>>>>
>>>>>> I don't see this functionality in the studio, and it has been removed
>>>>>> from the new ddbldr.
>>>>>
>>>>> The column settings you're asking about are actually DD class
>>>>> settings, not table settings. So they're available in the DD designer,
>>>>> not in the Table Editor.
>>>>>
>>>>> You can open a DD in the designer in several different ways, from
>>>>> Workspace Explorer -> Data Dictionaries and double-click the DD you
>>>>> want to open. Or you can open it from Table Explorer by finding the
>>>>> associated table and open up the treeview node labeled Data
>>>>> Dictionaries and double click the DD from there. Or you can open the
>>>>> DD from File -> Open File and browse to the DD, or any other means of
>>>>> opening source files. In any case, when you open the DD, it will now
>>>>> open in the DD designer as well as in the source code editor, just
>>>>> like when you open a view/dialog for example.
>>>>>
>>>>> -Sonny
>>>>>
>>>>
>>>>
>>>
>>>
>>
>>
>
>

Jim Albright
7-Oct-2008, 12:22 PM
Stephen,

I sent you 2 emails:
One with the 14.1 files
The other with the 14.0 files (previous 14.0 project).

Note: there is no DDClassList.xml in the newly created dd source folder.

Jim

"Stephen W. Meeley" <stephen-m@dataaccess.com> wrote in message
news:YYIw1WJKJHA.1980@dacmail.dataaccess.com...
> Hi Jim,
>
> We'll figure it out. Can you send me copies of your .sws and .ws files (both the 14.0 and the 14.1
> migrated versions) so I can understand your structure? Thanks.
>
> Also, in the 14.0 workspace, does everything model correctly? Do you have any warnings in the
> Problem Resolution panel?
>
> Best regards,
>
> -SWM-
>
> "Jim Albright" <jalbright@cfl.rr.com> wrote in message
> news:zUssdTJKJHA.7988@dacmail.dataaccess.com...
>> Stephen,
>>
>> I went back and:
>> 1. uninstalled Alpha 1 (using Windows Control Panel add/remove...)
>> 2. removed the registry entries (Hkey_LM and Hkey_CU)
>> 3. deleted the new project folder.
>>
>> Then I reinstalled Alpha 1.
>> I Opened the current 14.0 project in the new 14.1 studio, and migrated again.
>> Same result-- the DD files (in a brand new folder i.e. DD2008) were not changed.
>> There are no backup files (other than old ones from 14.0, BTW these got copied too), and the .DD
>> files all had the same date/time stamp as the 14.0 DD_SRC folder.
>>
>> The migration did parse all the .src files for DD items. But that was it.
>>
>> APCICTRL is a control/system file used in all the .src in this project. Confirmed.
>> All 245 .DD files are unchanged! The Migration program appears to have simply copied the .DD's
>> .FD's and .BAK's from the old DD folder.
>>
>> Since I have done this twice, I am either doing something wrong each time or this is not working
>> as designed.
>>
>> Jim
>>
>>
>> "Stephen W. Meeley" <stephen-m@dataaccess.com> wrote in message
>> news:Qm2PIzIKJHA.4840@dacmail.dataaccess.com...
>>> Hi Jim,
>>>
>>> All the data dictionaries that are used in any project in the source workspace should have been
>>> updated by the migration, and there should be a .bak file for all the updated files in the DDSrc
>>> folder. Can you verify that APCICTRL.DD is used in at least one of the projects in the workspace
>>> that you migrated? Also, can you please see if the .bak file exists (and if so, send us a copy
>>> of the .dd and the .bak file)?
>>>
>>> Best regards,
>>>
>>> -SWM-
>>>
>>>
>>> "Jim Albright" <jalbright@cfl.rr.com> wrote in message
>>> news:PHK6HsIKJHA.1636@dacmail.dataaccess.com...
>>>> Sonny,
>>>>
>>>> I forgot to mention that in the "Output" view, I get a message that says, "Could not parse the
>>>> Data Dictionary source file "APCICTRL.DD". This file may be an old style DD.
>>>> I was under the impress that the old style DD would be converted automatically when I migrated.
>>>>
>>>> Jim
>>>>
>>>> "Sonny Falk" <sonny-f@dataaccess.com> wrote in message
>>>> news:jkrlqDaJJHA.3324@dacmail.dataaccess.com...
>>>>>> In the previous dbbldg, we could go to the tab page marked "column settings". There we could
>>>>>> add settings like capslock, key field, default values, lookups, and masks.
>>>>>>
>>>>>> I don't see this functionality in the studio, and it has been removed from the new ddbldr.
>>>>>
>>>>> The column settings you're asking about are actually DD class settings, not table settings. So
>>>>> they're available in the DD designer, not in the Table Editor.
>>>>>
>>>>> You can open a DD in the designer in several different ways, from Workspace Explorer -> Data
>>>>> Dictionaries and double-click the DD you want to open. Or you can open it from Table Explorer
>>>>> by finding the associated table and open up the treeview node labeled Data Dictionaries and
>>>>> double click the DD from there. Or you can open the DD from File -> Open File and browse to
>>>>> the DD, or any other means of opening source files. In any case, when you open the DD, it will
>>>>> now open in the DD designer as well as in the source code editor, just like when you open a
>>>>> view/dialog for example.
>>>>>
>>>>> -Sonny
>>>>>
>>>>
>>>>
>>>
>>>
>>
>>
>
>

Jim Albright
7-Oct-2008, 12:24 PM
John,

The DDClassList.xml did not get copied or created in the new 14.1 DD source folder.
I can create this .xml using the ddBldr in 14.0 but I don't see that functionality in the newer
ddBldr (14.1).

Jim

"John van Houten" <john-h@dataaccess.com> wrote in message
news:GlcFRxJKJHA.1984@dacmail.dataaccess.com...
> Also usefull would be the DDClassList.xml file. It is possible that your .DD files are not
> registered in this list?
>
> regards John van Houten
>
>
> "Stephen W. Meeley" <stephen-m@dataaccess.com> wrote in message
> news:YYIw1WJKJHA.1980@dacmail.dataaccess.com...
>> Hi Jim,
>>
>> We'll figure it out. Can you send me copies of your .sws and .ws files (both the 14.0 and the
>> 14.1 migrated versions) so I can understand your structure? Thanks.
>>
>> Also, in the 14.0 workspace, does everything model correctly? Do you have any warnings in the
>> Problem Resolution panel?
>>
>> Best regards,
>>
>> -SWM-
>>
>> "Jim Albright" <jalbright@cfl.rr.com> wrote in message
>> news:zUssdTJKJHA.7988@dacmail.dataaccess.com...
>>> Stephen,
>>>
>>> I went back and:
>>> 1. uninstalled Alpha 1 (using Windows Control Panel add/remove...)
>>> 2. removed the registry entries (Hkey_LM and Hkey_CU)
>>> 3. deleted the new project folder.
>>>
>>> Then I reinstalled Alpha 1.
>>> I Opened the current 14.0 project in the new 14.1 studio, and migrated again.
>>> Same result-- the DD files (in a brand new folder i.e. DD2008) were not changed.
>>> There are no backup files (other than old ones from 14.0, BTW these got copied too), and the .DD
>>> files all had the same date/time stamp as the 14.0 DD_SRC folder.
>>>
>>> The migration did parse all the .src files for DD items. But that was it.
>>>
>>> APCICTRL is a control/system file used in all the .src in this project. Confirmed.
>>> All 245 .DD files are unchanged! The Migration program appears to have simply copied the .DD's
>>> .FD's and .BAK's from the old DD folder.
>>>
>>> Since I have done this twice, I am either doing something wrong each time or this is not working
>>> as designed.
>>>
>>> Jim
>>>
>>>
>>> "Stephen W. Meeley" <stephen-m@dataaccess.com> wrote in message
>>> news:Qm2PIzIKJHA.4840@dacmail.dataaccess.com...
>>>> Hi Jim,
>>>>
>>>> All the data dictionaries that are used in any project in the source workspace should have been
>>>> updated by the migration, and there should be a .bak file for all the updated files in the
>>>> DDSrc folder. Can you verify that APCICTRL.DD is used in at least one of the projects in the
>>>> workspace that you migrated? Also, can you please see if the .bak file exists (and if so, send
>>>> us a copy of the .dd and the .bak file)?
>>>>
>>>> Best regards,
>>>>
>>>> -SWM-
>>>>
>>>>
>>>> "Jim Albright" <jalbright@cfl.rr.com> wrote in message
>>>> news:PHK6HsIKJHA.1636@dacmail.dataaccess.com...
>>>>> Sonny,
>>>>>
>>>>> I forgot to mention that in the "Output" view, I get a message that says, "Could not parse the
>>>>> Data Dictionary source file "APCICTRL.DD". This file may be an old style DD.
>>>>> I was under the impress that the old style DD would be converted automatically when I
>>>>> migrated.
>>>>>
>>>>> Jim
>>>>>
>>>>> "Sonny Falk" <sonny-f@dataaccess.com> wrote in message
>>>>> news:jkrlqDaJJHA.3324@dacmail.dataaccess.com...
>>>>>>> In the previous dbbldg, we could go to the tab page marked "column settings". There we could
>>>>>>> add settings like capslock, key field, default values, lookups, and masks.
>>>>>>>
>>>>>>> I don't see this functionality in the studio, and it has been removed from the new ddbldr.
>>>>>>
>>>>>> The column settings you're asking about are actually DD class settings, not table settings.
>>>>>> So they're available in the DD designer, not in the Table Editor.
>>>>>>
>>>>>> You can open a DD in the designer in several different ways, from Workspace Explorer -> Data
>>>>>> Dictionaries and double-click the DD you want to open. Or you can open it from Table Explorer
>>>>>> by finding the associated table and open up the treeview node labeled Data Dictionaries and
>>>>>> double click the DD from there. Or you can open the DD from File -> Open File and browse to
>>>>>> the DD, or any other means of opening source files. In any case, when you open the DD, it
>>>>>> will now open in the DD designer as well as in the source code editor, just like when you
>>>>>> open a view/dialog for example.
>>>>>>
>>>>>> -Sonny
>>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>>
>>>
>>
>>
>

Stephen W. Meeley
7-Oct-2008, 02:31 PM
Jim,

Can you please resend and zip the files first? Our e-mail filter blocked one
message completely and removed the .ws file from the other.

Best regards,

-SWM-

"Jim Albright" <jalbright@cfl.rr.com> wrote in message
news:aBw8oFKKJHA.1980@dacmail.dataaccess.com...
> Stephen,
>
> I sent you 2 emails:
> One with the 14.1 files
> The other with the 14.0 files (previous 14.0 project).
>
> Note: there is no DDClassList.xml in the newly created dd source folder.
>
> Jim
>
> "Stephen W. Meeley" <stephen-m@dataaccess.com> wrote in message
> news:YYIw1WJKJHA.1980@dacmail.dataaccess.com...
>> Hi Jim,
>>
>> We'll figure it out. Can you send me copies of your .sws and .ws files
>> (both the 14.0 and the 14.1 migrated versions) so I can understand your
>> structure? Thanks.
>>
>> Also, in the 14.0 workspace, does everything model correctly? Do you have
>> any warnings in the Problem Resolution panel?
>>
>> Best regards,
>>
>> -SWM-
>>
>> "Jim Albright" <jalbright@cfl.rr.com> wrote in message
>> news:zUssdTJKJHA.7988@dacmail.dataaccess.com...
>>> Stephen,
>>>
>>> I went back and:
>>> 1. uninstalled Alpha 1 (using Windows Control Panel add/remove...)
>>> 2. removed the registry entries (Hkey_LM and Hkey_CU)
>>> 3. deleted the new project folder.
>>>
>>> Then I reinstalled Alpha 1.
>>> I Opened the current 14.0 project in the new 14.1 studio, and migrated
>>> again.
>>> Same result-- the DD files (in a brand new folder i.e. DD2008) were not
>>> changed.
>>> There are no backup files (other than old ones from 14.0, BTW these got
>>> copied too), and the .DD files all had the same date/time stamp as the
>>> 14.0 DD_SRC folder.
>>>
>>> The migration did parse all the .src files for DD items. But that was
>>> it.
>>>
>>> APCICTRL is a control/system file used in all the .src in this project.
>>> Confirmed.
>>> All 245 .DD files are unchanged! The Migration program appears to have
>>> simply copied the .DD's .FD's and .BAK's from the old DD folder.
>>>
>>> Since I have done this twice, I am either doing something wrong each
>>> time or this is not working as designed.
>>>
>>> Jim
>>>
>>>
>>> "Stephen W. Meeley" <stephen-m@dataaccess.com> wrote in message
>>> news:Qm2PIzIKJHA.4840@dacmail.dataaccess.com...
>>>> Hi Jim,
>>>>
>>>> All the data dictionaries that are used in any project in the source
>>>> workspace should have been updated by the migration, and there should
>>>> be a .bak file for all the updated files in the DDSrc folder. Can you
>>>> verify that APCICTRL.DD is used in at least one of the projects in the
>>>> workspace that you migrated? Also, can you please see if the .bak file
>>>> exists (and if so, send us a copy of the .dd and the .bak file)?
>>>>
>>>> Best regards,
>>>>
>>>> -SWM-
>>>>
>>>>
>>>> "Jim Albright" <jalbright@cfl.rr.com> wrote in message
>>>> news:PHK6HsIKJHA.1636@dacmail.dataaccess.com...
>>>>> Sonny,
>>>>>
>>>>> I forgot to mention that in the "Output" view, I get a message that
>>>>> says, "Could not parse the Data Dictionary source file "APCICTRL.DD".
>>>>> This file may be an old style DD.
>>>>> I was under the impress that the old style DD would be converted
>>>>> automatically when I migrated.
>>>>>
>>>>> Jim
>>>>>
>>>>> "Sonny Falk" <sonny-f@dataaccess.com> wrote in message
>>>>> news:jkrlqDaJJHA.3324@dacmail.dataaccess.com...
>>>>>>> In the previous dbbldg, we could go to the tab page marked "column
>>>>>>> settings". There we could add settings like capslock, key field,
>>>>>>> default values, lookups, and masks.
>>>>>>>
>>>>>>> I don't see this functionality in the studio, and it has been
>>>>>>> removed from the new ddbldr.
>>>>>>
>>>>>> The column settings you're asking about are actually DD class
>>>>>> settings, not table settings. So they're available in the DD
>>>>>> designer, not in the Table Editor.
>>>>>>
>>>>>> You can open a DD in the designer in several different ways, from
>>>>>> Workspace Explorer -> Data Dictionaries and double-click the DD you
>>>>>> want to open. Or you can open it from Table Explorer by finding the
>>>>>> associated table and open up the treeview node labeled Data
>>>>>> Dictionaries and double click the DD from there. Or you can open the
>>>>>> DD from File -> Open File and browse to the DD, or any other means of
>>>>>> opening source files. In any case, when you open the DD, it will now
>>>>>> open in the DD designer as well as in the source code editor, just
>>>>>> like when you open a view/dialog for example.
>>>>>>
>>>>>> -Sonny
>>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>>
>>>
>>
>>
>
>

Stephen W. Meeley
7-Oct-2008, 04:37 PM
Hi Jim,

I got the files you resent and found the cause of the problem. The migration
is not properly handling the DDs when an external location is used. It is
detecting the external location and properly allowing you to copy them to
another external location for migration, but then it's not doing the
migration properly after the copy and, if you examine the workspace pathing,
the path to the new external location is pretty messy (it looks like the
migration tried to convert it to a relative path).

We'll try to get this fixed for the next Alpha build. In the meantime, if
you don't want this to hold up your experimenting, you can do this:

* In the 14.0 workspace, bring a copy of the external DDSrc folder into the
default location in the workspace structure (a DDSrc subfolder)
* Edit the .ws file to reflect the temporary relative location (.\DDSrc)
* Run the migration again (you should not see any messages about the DDSrc
being external)
* Check to see that the DDs are successfully migration and model in the
Studio

Thanks for the report.

Best regards,

-SWM-


"Stephen W. Meeley" <stephen-m@dataaccess.com> wrote in message
news:AjCHBNLKJHA.7988@dacmail.dataaccess.com...
> Jim,
>
> Can you please resend and zip the files first? Our e-mail filter blocked
> one message completely and removed the .ws file from the other.
>
> Best regards,
>
> -SWM-
>
> "Jim Albright" <jalbright@cfl.rr.com> wrote in message
> news:aBw8oFKKJHA.1980@dacmail.dataaccess.com...
>> Stephen,
>>
>> I sent you 2 emails:
>> One with the 14.1 files
>> The other with the 14.0 files (previous 14.0 project).
>>
>> Note: there is no DDClassList.xml in the newly created dd source folder.
>>
>> Jim
>>
>> "Stephen W. Meeley" <stephen-m@dataaccess.com> wrote in message
>> news:YYIw1WJKJHA.1980@dacmail.dataaccess.com...
>>> Hi Jim,
>>>
>>> We'll figure it out. Can you send me copies of your .sws and .ws files
>>> (both the 14.0 and the 14.1 migrated versions) so I can understand your
>>> structure? Thanks.
>>>
>>> Also, in the 14.0 workspace, does everything model correctly? Do you
>>> have any warnings in the Problem Resolution panel?
>>>
>>> Best regards,
>>>
>>> -SWM-
>>>
>>> "Jim Albright" <jalbright@cfl.rr.com> wrote in message
>>> news:zUssdTJKJHA.7988@dacmail.dataaccess.com...
>>>> Stephen,
>>>>
>>>> I went back and:
>>>> 1. uninstalled Alpha 1 (using Windows Control Panel add/remove...)
>>>> 2. removed the registry entries (Hkey_LM and Hkey_CU)
>>>> 3. deleted the new project folder.
>>>>
>>>> Then I reinstalled Alpha 1.
>>>> I Opened the current 14.0 project in the new 14.1 studio, and migrated
>>>> again.
>>>> Same result-- the DD files (in a brand new folder i.e. DD2008) were not
>>>> changed.
>>>> There are no backup files (other than old ones from 14.0, BTW these got
>>>> copied too), and the .DD files all had the same date/time stamp as the
>>>> 14.0 DD_SRC folder.
>>>>
>>>> The migration did parse all the .src files for DD items. But that was
>>>> it.
>>>>
>>>> APCICTRL is a control/system file used in all the .src in this project.
>>>> Confirmed.
>>>> All 245 .DD files are unchanged! The Migration program appears to have
>>>> simply copied the .DD's .FD's and .BAK's from the old DD folder.
>>>>
>>>> Since I have done this twice, I am either doing something wrong each
>>>> time or this is not working as designed.
>>>>
>>>> Jim
>>>>
>>>>
>>>> "Stephen W. Meeley" <stephen-m@dataaccess.com> wrote in message
>>>> news:Qm2PIzIKJHA.4840@dacmail.dataaccess.com...
>>>>> Hi Jim,
>>>>>
>>>>> All the data dictionaries that are used in any project in the source
>>>>> workspace should have been updated by the migration, and there should
>>>>> be a .bak file for all the updated files in the DDSrc folder. Can you
>>>>> verify that APCICTRL.DD is used in at least one of the projects in the
>>>>> workspace that you migrated? Also, can you please see if the .bak file
>>>>> exists (and if so, send us a copy of the .dd and the .bak file)?
>>>>>
>>>>> Best regards,
>>>>>
>>>>> -SWM-
>>>>>
>>>>>
>>>>> "Jim Albright" <jalbright@cfl.rr.com> wrote in message
>>>>> news:PHK6HsIKJHA.1636@dacmail.dataaccess.com...
>>>>>> Sonny,
>>>>>>
>>>>>> I forgot to mention that in the "Output" view, I get a message that
>>>>>> says, "Could not parse the Data Dictionary source file "APCICTRL.DD".
>>>>>> This file may be an old style DD.
>>>>>> I was under the impress that the old style DD would be converted
>>>>>> automatically when I migrated.
>>>>>>
>>>>>> Jim
>>>>>>
>>>>>> "Sonny Falk" <sonny-f@dataaccess.com> wrote in message
>>>>>> news:jkrlqDaJJHA.3324@dacmail.dataaccess.com...
>>>>>>>> In the previous dbbldg, we could go to the tab page marked "column
>>>>>>>> settings". There we could add settings like capslock, key field,
>>>>>>>> default values, lookups, and masks.
>>>>>>>>
>>>>>>>> I don't see this functionality in the studio, and it has been
>>>>>>>> removed from the new ddbldr.
>>>>>>>
>>>>>>> The column settings you're asking about are actually DD class
>>>>>>> settings, not table settings. So they're available in the DD
>>>>>>> designer, not in the Table Editor.
>>>>>>>
>>>>>>> You can open a DD in the designer in several different ways, from
>>>>>>> Workspace Explorer -> Data Dictionaries and double-click the DD you
>>>>>>> want to open. Or you can open it from Table Explorer by finding the
>>>>>>> associated table and open up the treeview node labeled Data
>>>>>>> Dictionaries and double click the DD from there. Or you can open the
>>>>>>> DD from File -> Open File and browse to the DD, or any other means
>>>>>>> of opening source files. In any case, when you open the DD, it will
>>>>>>> now open in the DD designer as well as in the source code editor,
>>>>>>> just like when you open a view/dialog for example.
>>>>>>>
>>>>>>> -Sonny
>>>>>>>
>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>>
>>>
>>
>>
>
>

Jim Albright
7-Oct-2008, 05:32 PM
Stephen,

Thanks for the quick response. I had used the network location of the DDsrc since it is common to
the Web server also (which is still running under VDF v12.0). I have a separate computer to develop
the web site from the one I use for the production .exe's.

I will do as you suggested.

Eagerly awaiting the next release. Thanks.

Jim

"Stephen W. Meeley" <stephen-m@dataaccess.com> wrote in message
news:3H$4wTMKJHA.7988@dacmail.dataaccess.com...
> Hi Jim,
>
> I got the files you resent and found the cause of the problem. The migration is not properly
> handling the DDs when an external location is used. It is detecting the external location and
> properly allowing you to copy them to another external location for migration, but then it's not
> doing the migration properly after the copy and, if you examine the workspace pathing, the path to
> the new external location is pretty messy (it looks like the migration tried to convert it to a
> relative path).
>
> We'll try to get this fixed for the next Alpha build. In the meantime, if you don't want this to
> hold up your experimenting, you can do this:
>
> * In the 14.0 workspace, bring a copy of the external DDSrc folder into the default location in
> the workspace structure (a DDSrc subfolder)
> * Edit the .ws file to reflect the temporary relative location (.\DDSrc)
> * Run the migration again (you should not see any messages about the DDSrc being external)
> * Check to see that the DDs are successfully migration and model in the Studio
>
> Thanks for the report.
>
> Best regards,
>
> -SWM-
>
>
> "Stephen W. Meeley" <stephen-m@dataaccess.com> wrote in message
> news:AjCHBNLKJHA.7988@dacmail.dataaccess.com...
>> Jim,
>>
>> Can you please resend and zip the files first? Our e-mail filter blocked one message completely
>> and removed the .ws file from the other.
>>
>> Best regards,
>>
>> -SWM-
>>
>> "Jim Albright" <jalbright@cfl.rr.com> wrote in message
>> news:aBw8oFKKJHA.1980@dacmail.dataaccess.com...
>>> Stephen,
>>>
>>> I sent you 2 emails:
>>> One with the 14.1 files
>>> The other with the 14.0 files (previous 14.0 project).
>>>
>>> Note: there is no DDClassList.xml in the newly created dd source folder.
>>>
>>> Jim
>>>
>>> "Stephen W. Meeley" <stephen-m@dataaccess.com> wrote in message
>>> news:YYIw1WJKJHA.1980@dacmail.dataaccess.com...
>>>> Hi Jim,
>>>>
>>>> We'll figure it out. Can you send me copies of your .sws and .ws files (both the 14.0 and the
>>>> 14.1 migrated versions) so I can understand your structure? Thanks.
>>>>
>>>> Also, in the 14.0 workspace, does everything model correctly? Do you have any warnings in the
>>>> Problem Resolution panel?
>>>>
>>>> Best regards,
>>>>
>>>> -SWM-
>>>>
>>>> "Jim Albright" <jalbright@cfl.rr.com> wrote in message
>>>> news:zUssdTJKJHA.7988@dacmail.dataaccess.com...
>>>>> Stephen,
>>>>>
>>>>> I went back and:
>>>>> 1. uninstalled Alpha 1 (using Windows Control Panel add/remove...)
>>>>> 2. removed the registry entries (Hkey_LM and Hkey_CU)
>>>>> 3. deleted the new project folder.
>>>>>
>>>>> Then I reinstalled Alpha 1.
>>>>> I Opened the current 14.0 project in the new 14.1 studio, and migrated again.
>>>>> Same result-- the DD files (in a brand new folder i.e. DD2008) were not changed.
>>>>> There are no backup files (other than old ones from 14.0, BTW these got copied too), and the
>>>>> .DD files all had the same date/time stamp as the 14.0 DD_SRC folder.
>>>>>
>>>>> The migration did parse all the .src files for DD items. But that was it.
>>>>>
>>>>> APCICTRL is a control/system file used in all the .src in this project. Confirmed.
>>>>> All 245 .DD files are unchanged! The Migration program appears to have simply copied the .DD's
>>>>> .FD's and .BAK's from the old DD folder.
>>>>>
>>>>> Since I have done this twice, I am either doing something wrong each time or this is not
>>>>> working as designed.
>>>>>
>>>>> Jim
>>>>>
>>>>>
>>>>> "Stephen W. Meeley" <stephen-m@dataaccess.com> wrote in message
>>>>> news:Qm2PIzIKJHA.4840@dacmail.dataaccess.com...
>>>>>> Hi Jim,
>>>>>>
>>>>>> All the data dictionaries that are used in any project in the source workspace should have
>>>>>> been updated by the migration, and there should be a .bak file for all the updated files in
>>>>>> the DDSrc folder. Can you verify that APCICTRL.DD is used in at least one of the projects in
>>>>>> the workspace that you migrated? Also, can you please see if the .bak file exists (and if so,
>>>>>> send us a copy of the .dd and the .bak file)?
>>>>>>
>>>>>> Best regards,
>>>>>>
>>>>>> -SWM-
>>>>>>
>>>>>>
>>>>>> "Jim Albright" <jalbright@cfl.rr.com> wrote in message
>>>>>> news:PHK6HsIKJHA.1636@dacmail.dataaccess.com...
>>>>>>> Sonny,
>>>>>>>
>>>>>>> I forgot to mention that in the "Output" view, I get a message that says, "Could not parse
>>>>>>> the Data Dictionary source file "APCICTRL.DD". This file may be an old style DD.
>>>>>>> I was under the impress that the old style DD would be converted automatically when I
>>>>>>> migrated.
>>>>>>>
>>>>>>> Jim
>>>>>>>
>>>>>>> "Sonny Falk" <sonny-f@dataaccess.com> wrote in message
>>>>>>> news:jkrlqDaJJHA.3324@dacmail.dataaccess.com...
>>>>>>>>> In the previous dbbldg, we could go to the tab page marked "column settings". There we
>>>>>>>>> could add settings like capslock, key field, default values, lookups, and masks.
>>>>>>>>>
>>>>>>>>> I don't see this functionality in the studio, and it has been removed from the new ddbldr.
>>>>>>>>
>>>>>>>> The column settings you're asking about are actually DD class settings, not table settings.
>>>>>>>> So they're available in the DD designer, not in the Table Editor.
>>>>>>>>
>>>>>>>> You can open a DD in the designer in several different ways, from Workspace Explorer ->
>>>>>>>> Data Dictionaries and double-click the DD you want to open. Or you can open it from Table
>>>>>>>> Explorer by finding the associated table and open up the treeview node labeled Data
>>>>>>>> Dictionaries and double click the DD from there. Or you can open the DD from File -> Open
>>>>>>>> File and browse to the DD, or any other means of opening source files. In any case, when
>>>>>>>> you open the DD, it will now open in the DD designer as well as in the source code editor,
>>>>>>>> just like when you open a view/dialog for example.
>>>>>>>>
>>>>>>>> -Sonny
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>>
>>>
>>
>>
>
>

Dave Robinson
8-Oct-2008, 08:39 AM
Stephen,

Thanks for this revelation.

I was playing with migration at the weekend and got what seemed to be an incomplete mig of my 'DDSrc' folder. I've a similar structure to Jim (us Novellites tread our own path <g>).
I share my DDsrc, actually called FD and at a higher level in by Dev structure, between two main projects and all versions of DF and VDF.

I blew away the results (and its on my home machine) so can't give chapter and verse but that might explain what happened.

Looks like I'm going to have to have at least a version-specific DDsrc in future.

BTW: Please don't introduce anything in DDsrc files that screws up char mode compatibility, the CM-VDF migration is only in its tenth year and I've some way to go :D.

Dave

Stephen W. Meeley
8-Oct-2008, 09:07 AM
Hi Dave,

Trying to keep the same code (DDs or anything) viable (which can be more
than just "does it compile?") across all versions of DF and VDF is always
hard to do, and can be extremely limiting. You basically have to play to the
lowest common denominator (essentially forgoing all the enhancements over
the years) and that's assuming you can even clearly define what the LCD even
is. Even when code compiles in all environments, that's no guarantee that it
will execute the same - changes often involve multiple layers of the system
in combination; runtime, FMAC, package, etc. The latest changes to DDs in
14.1 are a good example - you can't compile or use the new style DDs in
older environmtments. You can still compile and use the old style DDs in the
new environment, but then they don't model and you don't get any of the new
capabilities in the Studio and are forced to maintain them the old way (in
the LCD revision of Database Builder) - ugh! We certainly recommend that you
do migrate the DDs and then use them to their fullest extent in 14.1. Tools
like Beyond Compare can help you synchronize necessary changes between the
old and new sets.

Best regards,

-SWM-


"Dave Robinson" <dr at kirkfreeport.net> wrote in message
news:tv%23VDtUKJHA.1636@dacmail.dataaccess.com...
> Stephen,
>
> Thanks for this revelation.
>
> I was playing with migration at the weekend and got what seemed to be an
> incomplete mig of my 'DDSrc' folder. I've a similar structure to Jim (us
> Novellites tread our own path <g>).
> I share my DDsrc, actually called FD and at a higher level in by Dev
> structure, between two main projects and all versions of DF and VDF.
>
> I blew away the results (and its on my home machine) so can't give chapter
> and verse but that might explain what happened.
>
> Looks like I'm going to have to have at least a version-specific DDsrc in
> future.
>
> BTW: Please don't introduce anything in DDsrc files that screws up char
> mode compatibility, the CM-VDF migration is only in its tenth year and
> I've some way to go :D.
>
> Dave

Jim Albright
8-Oct-2008, 09:18 AM
Stephen,

Creating the DDsrc on the local drive worked. I then moved the folder to the server and changed the
workspace to reflect the new path. That worked.

Thanks,

Jim

"Jim Albright" <jalbright@cfl.rr.com> wrote in message
news:J3xxvyMKJHA.1636@dacmail.dataaccess.com...
> Stephen,
>
> Thanks for the quick response. I had used the network location of the DDsrc since it is common to
> the Web server also (which is still running under VDF v12.0). I have a separate computer to
> develop the web site from the one I use for the production .exe's.
>
> I will do as you suggested.
>
> Eagerly awaiting the next release. Thanks.
>
> Jim
>
> "Stephen W. Meeley" <stephen-m@dataaccess.com> wrote in message
> news:3H$4wTMKJHA.7988@dacmail.dataaccess.com...
>> Hi Jim,
>>
>> I got the files you resent and found the cause of the problem. The migration is not properly
>> handling the DDs when an external location is used. It is detecting the external location and
>> properly allowing you to copy them to another external location for migration, but then it's not
>> doing the migration properly after the copy and, if you examine the workspace pathing, the path
>> to the new external location is pretty messy (it looks like the migration tried to convert it to
>> a relative path).
>>
>> We'll try to get this fixed for the next Alpha build. In the meantime, if you don't want this to
>> hold up your experimenting, you can do this:
>>
>> * In the 14.0 workspace, bring a copy of the external DDSrc folder into the default location in
>> the workspace structure (a DDSrc subfolder)
>> * Edit the .ws file to reflect the temporary relative location (.\DDSrc)
>> * Run the migration again (you should not see any messages about the DDSrc being external)
>> * Check to see that the DDs are successfully migration and model in the Studio
>>
>> Thanks for the report.
>>
>> Best regards,
>>
>> -SWM-
>>
>>
>> "Stephen W. Meeley" <stephen-m@dataaccess.com> wrote in message
>> news:AjCHBNLKJHA.7988@dacmail.dataaccess.com...
>>> Jim,
>>>
>>> Can you please resend and zip the files first? Our e-mail filter blocked one message completely
>>> and removed the .ws file from the other.
>>>
>>> Best regards,
>>>
>>> -SWM-
>>>
>>> "Jim Albright" <jalbright@cfl.rr.com> wrote in message
>>> news:aBw8oFKKJHA.1980@dacmail.dataaccess.com...
>>>> Stephen,
>>>>
>>>> I sent you 2 emails:
>>>> One with the 14.1 files
>>>> The other with the 14.0 files (previous 14.0 project).
>>>>
>>>> Note: there is no DDClassList.xml in the newly created dd source folder.
>>>>
>>>> Jim
>>>>
>>>> "Stephen W. Meeley" <stephen-m@dataaccess.com> wrote in message
>>>> news:YYIw1WJKJHA.1980@dacmail.dataaccess.com...
>>>>> Hi Jim,
>>>>>
>>>>> We'll figure it out. Can you send me copies of your .sws and .ws files (both the 14.0 and the
>>>>> 14.1 migrated versions) so I can understand your structure? Thanks.
>>>>>
>>>>> Also, in the 14.0 workspace, does everything model correctly? Do you have any warnings in the
>>>>> Problem Resolution panel?
>>>>>
>>>>> Best regards,
>>>>>
>>>>> -SWM-
>>>>>
>>>>> "Jim Albright" <jalbright@cfl.rr.com> wrote in message
>>>>> news:zUssdTJKJHA.7988@dacmail.dataaccess.com...
>>>>>> Stephen,
>>>>>>
>>>>>> I went back and:
>>>>>> 1. uninstalled Alpha 1 (using Windows Control Panel add/remove...)
>>>>>> 2. removed the registry entries (Hkey_LM and Hkey_CU)
>>>>>> 3. deleted the new project folder.
>>>>>>
>>>>>> Then I reinstalled Alpha 1.
>>>>>> I Opened the current 14.0 project in the new 14.1 studio, and migrated again.
>>>>>> Same result-- the DD files (in a brand new folder i.e. DD2008) were not changed.
>>>>>> There are no backup files (other than old ones from 14.0, BTW these got copied too), and the
>>>>>> .DD files all had the same date/time stamp as the 14.0 DD_SRC folder.
>>>>>>
>>>>>> The migration did parse all the .src files for DD items. But that was it.
>>>>>>
>>>>>> APCICTRL is a control/system file used in all the .src in this project. Confirmed.
>>>>>> All 245 .DD files are unchanged! The Migration program appears to have simply copied the
>>>>>> .DD's .FD's and .BAK's from the old DD folder.
>>>>>>
>>>>>> Since I have done this twice, I am either doing something wrong each time or this is not
>>>>>> working as designed.
>>>>>>
>>>>>> Jim
>>>>>>
>>>>>>
>>>>>> "Stephen W. Meeley" <stephen-m@dataaccess.com> wrote in message
>>>>>> news:Qm2PIzIKJHA.4840@dacmail.dataaccess.com...
>>>>>>> Hi Jim,
>>>>>>>
>>>>>>> All the data dictionaries that are used in any project in the source workspace should have
>>>>>>> been updated by the migration, and there should be a .bak file for all the updated files in
>>>>>>> the DDSrc folder. Can you verify that APCICTRL.DD is used in at least one of the projects in
>>>>>>> the workspace that you migrated? Also, can you please see if the .bak file exists (and if
>>>>>>> so, send us a copy of the .dd and the .bak file)?
>>>>>>>
>>>>>>> Best regards,
>>>>>>>
>>>>>>> -SWM-
>>>>>>>
>>>>>>>
>>>>>>> "Jim Albright" <jalbright@cfl.rr.com> wrote in message
>>>>>>> news:PHK6HsIKJHA.1636@dacmail.dataaccess.com...
>>>>>>>> Sonny,
>>>>>>>>
>>>>>>>> I forgot to mention that in the "Output" view, I get a message that says, "Could not parse
>>>>>>>> the Data Dictionary source file "APCICTRL.DD". This file may be an old style DD.
>>>>>>>> I was under the impress that the old style DD would be converted automatically when I
>>>>>>>> migrated.
>>>>>>>>
>>>>>>>> Jim
>>>>>>>>
>>>>>>>> "Sonny Falk" <sonny-f@dataaccess.com> wrote in message
>>>>>>>> news:jkrlqDaJJHA.3324@dacmail.dataaccess.com...
>>>>>>>>>> In the previous dbbldg, we could go to the tab page marked "column settings". There we
>>>>>>>>>> could add settings like capslock, key field, default values, lookups, and masks.
>>>>>>>>>>
>>>>>>>>>> I don't see this functionality in the studio, and it has been removed from the new
>>>>>>>>>> ddbldr.
>>>>>>>>>
>>>>>>>>> The column settings you're asking about are actually DD class settings, not table
>>>>>>>>> settings. So they're available in the DD designer, not in the Table Editor.
>>>>>>>>>
>>>>>>>>> You can open a DD in the designer in several different ways, from Workspace Explorer ->
>>>>>>>>> Data Dictionaries and double-click the DD you want to open. Or you can open it from Table
>>>>>>>>> Explorer by finding the associated table and open up the treeview node labeled Data
>>>>>>>>> Dictionaries and double click the DD from there. Or you can open the DD from File -> Open
>>>>>>>>> File and browse to the DD, or any other means of opening source files. In any case, when
>>>>>>>>> you open the DD, it will now open in the DD designer as well as in the source code editor,
>>>>>>>>> just like when you open a view/dialog for example.
>>>>>>>>>
>>>>>>>>> -Sonny
>>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>>
>>>
>>
>>
>
>

Dave Robinson
8-Oct-2008, 09:42 AM
point(s) taken and in another 10 years or so I'll be charmode-free <g>.

D

Stephen W. Meeley
8-Oct-2008, 09:45 AM
Great!

Best regards,

-SWM-

"Jim Albright" <jalbright@cfl.rr.com> wrote in message
news:$gYWXDVKJHA.1980@dacmail.dataaccess.com...
> Stephen,
>
> Creating the DDsrc on the local drive worked. I then moved the folder to
> the server and changed the workspace to reflect the new path. That worked.
>
> Thanks,
>
> Jim
>
> "Jim Albright" <jalbright@cfl.rr.com> wrote in message
> news:J3xxvyMKJHA.1636@dacmail.dataaccess.com...
>> Stephen,
>>
>> Thanks for the quick response. I had used the network location of the
>> DDsrc since it is common to the Web server also (which is still running
>> under VDF v12.0). I have a separate computer to develop the web site from
>> the one I use for the production .exe's.
>>
>> I will do as you suggested.
>>
>> Eagerly awaiting the next release. Thanks.
>>
>> Jim
>>
>> "Stephen W. Meeley" <stephen-m@dataaccess.com> wrote in message
>> news:3H$4wTMKJHA.7988@dacmail.dataaccess.com...
>>> Hi Jim,
>>>
>>> I got the files you resent and found the cause of the problem. The
>>> migration is not properly handling the DDs when an external location is
>>> used. It is detecting the external location and properly allowing you to
>>> copy them to another external location for migration, but then it's not
>>> doing the migration properly after the copy and, if you examine the
>>> workspace pathing, the path to the new external location is pretty messy
>>> (it looks like the migration tried to convert it to a relative path).
>>>
>>> We'll try to get this fixed for the next Alpha build. In the meantime,
>>> if you don't want this to hold up your experimenting, you can do this:
>>>
>>> * In the 14.0 workspace, bring a copy of the external DDSrc folder into
>>> the default location in the workspace structure (a DDSrc subfolder)
>>> * Edit the .ws file to reflect the temporary relative location (.\DDSrc)
>>> * Run the migration again (you should not see any messages about the
>>> DDSrc being external)
>>> * Check to see that the DDs are successfully migration and model in the
>>> Studio
>>>
>>> Thanks for the report.
>>>
>>> Best regards,
>>>
>>> -SWM-
>>>
>>>
>>> "Stephen W. Meeley" <stephen-m@dataaccess.com> wrote in message
>>> news:AjCHBNLKJHA.7988@dacmail.dataaccess.com...
>>>> Jim,
>>>>
>>>> Can you please resend and zip the files first? Our e-mail filter
>>>> blocked one message completely and removed the .ws file from the other.
>>>>
>>>> Best regards,
>>>>
>>>> -SWM-
>>>>
>>>> "Jim Albright" <jalbright@cfl.rr.com> wrote in message
>>>> news:aBw8oFKKJHA.1980@dacmail.dataaccess.com...
>>>>> Stephen,
>>>>>
>>>>> I sent you 2 emails:
>>>>> One with the 14.1 files
>>>>> The other with the 14.0 files (previous 14.0 project).
>>>>>
>>>>> Note: there is no DDClassList.xml in the newly created dd source
>>>>> folder.
>>>>>
>>>>> Jim
>>>>>
>>>>> "Stephen W. Meeley" <stephen-m@dataaccess.com> wrote in message
>>>>> news:YYIw1WJKJHA.1980@dacmail.dataaccess.com...
>>>>>> Hi Jim,
>>>>>>
>>>>>> We'll figure it out. Can you send me copies of your .sws and .ws
>>>>>> files (both the 14.0 and the 14.1 migrated versions) so I can
>>>>>> understand your structure? Thanks.
>>>>>>
>>>>>> Also, in the 14.0 workspace, does everything model correctly? Do you
>>>>>> have any warnings in the Problem Resolution panel?
>>>>>>
>>>>>> Best regards,
>>>>>>
>>>>>> -SWM-
>>>>>>
>>>>>> "Jim Albright" <jalbright@cfl.rr.com> wrote in message
>>>>>> news:zUssdTJKJHA.7988@dacmail.dataaccess.com...
>>>>>>> Stephen,
>>>>>>>
>>>>>>> I went back and:
>>>>>>> 1. uninstalled Alpha 1 (using Windows Control Panel add/remove...)
>>>>>>> 2. removed the registry entries (Hkey_LM and Hkey_CU)
>>>>>>> 3. deleted the new project folder.
>>>>>>>
>>>>>>> Then I reinstalled Alpha 1.
>>>>>>> I Opened the current 14.0 project in the new 14.1 studio, and
>>>>>>> migrated again.
>>>>>>> Same result-- the DD files (in a brand new folder i.e. DD2008) were
>>>>>>> not changed.
>>>>>>> There are no backup files (other than old ones from 14.0, BTW these
>>>>>>> got copied too), and the .DD files all had the same date/time stamp
>>>>>>> as the 14.0 DD_SRC folder.
>>>>>>>
>>>>>>> The migration did parse all the .src files for DD items. But that
>>>>>>> was it.
>>>>>>>
>>>>>>> APCICTRL is a control/system file used in all the .src in this
>>>>>>> project. Confirmed.
>>>>>>> All 245 .DD files are unchanged! The Migration program appears to
>>>>>>> have simply copied the .DD's .FD's and .BAK's from the old DD
>>>>>>> folder.
>>>>>>>
>>>>>>> Since I have done this twice, I am either doing something wrong each
>>>>>>> time or this is not working as designed.
>>>>>>>
>>>>>>> Jim
>>>>>>>
>>>>>>>
>>>>>>> "Stephen W. Meeley" <stephen-m@dataaccess.com> wrote in message
>>>>>>> news:Qm2PIzIKJHA.4840@dacmail.dataaccess.com...
>>>>>>>> Hi Jim,
>>>>>>>>
>>>>>>>> All the data dictionaries that are used in any project in the
>>>>>>>> source workspace should have been updated by the migration, and
>>>>>>>> there should be a .bak file for all the updated files in the DDSrc
>>>>>>>> folder. Can you verify that APCICTRL.DD is used in at least one of
>>>>>>>> the projects in the workspace that you migrated? Also, can you
>>>>>>>> please see if the .bak file exists (and if so, send us a copy of
>>>>>>>> the .dd and the .bak file)?
>>>>>>>>
>>>>>>>> Best regards,
>>>>>>>>
>>>>>>>> -SWM-
>>>>>>>>
>>>>>>>>
>>>>>>>> "Jim Albright" <jalbright@cfl.rr.com> wrote in message
>>>>>>>> news:PHK6HsIKJHA.1636@dacmail.dataaccess.com...
>>>>>>>>> Sonny,
>>>>>>>>>
>>>>>>>>> I forgot to mention that in the "Output" view, I get a message
>>>>>>>>> that says, "Could not parse the Data Dictionary source file
>>>>>>>>> "APCICTRL.DD". This file may be an old style DD.
>>>>>>>>> I was under the impress that the old style DD would be converted
>>>>>>>>> automatically when I migrated.
>>>>>>>>>
>>>>>>>>> Jim
>>>>>>>>>
>>>>>>>>> "Sonny Falk" <sonny-f@dataaccess.com> wrote in message
>>>>>>>>> news:jkrlqDaJJHA.3324@dacmail.dataaccess.com...
>>>>>>>>>>> In the previous dbbldg, we could go to the tab page marked
>>>>>>>>>>> "column settings". There we could add settings like capslock,
>>>>>>>>>>> key field, default values, lookups, and masks.
>>>>>>>>>>>
>>>>>>>>>>> I don't see this functionality in the studio, and it has been
>>>>>>>>>>> removed from the new ddbldr.
>>>>>>>>>>
>>>>>>>>>> The column settings you're asking about are actually DD class
>>>>>>>>>> settings, not table settings. So they're available in the DD
>>>>>>>>>> designer, not in the Table Editor.
>>>>>>>>>>
>>>>>>>>>> You can open a DD in the designer in several different ways, from
>>>>>>>>>> Workspace Explorer -> Data Dictionaries and double-click the DD
>>>>>>>>>> you want to open. Or you can open it from Table Explorer by
>>>>>>>>>> finding the associated table and open up the treeview node
>>>>>>>>>> labeled Data Dictionaries and double click the DD from there. Or
>>>>>>>>>> you can open the DD from File -> Open File and browse to the DD,
>>>>>>>>>> or any other means of opening source files. In any case, when you
>>>>>>>>>> open the DD, it will now open in the DD designer as well as in
>>>>>>>>>> the source code editor, just like when you open a view/dialog for
>>>>>>>>>> example.
>>>>>>>>>>
>>>>>>>>>> -Sonny
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>>
>>>
>>
>>
>
>