PD dependant files, supporting files and names.

[Richard Torrens (lists)]

The latest Pd 4.50/35 (23-Mar-2012) seems to have a problem with dependant
files etc.

I have a central database simply called " " - that's a single hard space.

It does not get automatically loaded.

Suspecting this is a problem with hard-space in a file name, I renamed it
to DB.

None of its supporting files get renamed.

So is there a change in the way PD handles hard spaces in file names?

--
Richard Torrens.
http://www.Torrens.org.uk for genealogy, natural history, wild food, walks, cats
and more!

[Richard Torrens (lists)]

To add to my own posting:

On 29 Apr, Li...@Torrens.org.uk wrote:
> The latest Pd 4.50/35 (23-Mar-2012) seems to have a problem with
> dependant files etc.

> I have a central database simply called " " - that's a single hard space.

> It does not get automatically loaded.

> Suspecting this is a problem with hard-space in a file name, I renamed
> it to DB.

> None of its supporting files get renamed.

> So is there a change in the way PD handles hard spaces in file names?

There is more to this: latest PD appears to be broken in its ability to
load dependent documents!

I have changed several thousand files (thank you StrongED) to change the
file name 2 " to "DB"

/23 has no problem loading all required files.
/35 does not do so.

There are changes in the !Boot file (including some of my own additions to
make the system work on any computer in our network) which I have
investigated and I cannot see that the problem is there - all relevant
paths seem to be recorded in the SysVar
PipeDream$Path(Macro) :
<PipeDream$UserPath>,<PipeDream$ResourceDir>.User.,<PipeDream$ResourceDir>.Resource.

But there could be a problem searching this path.

[Stuart Swales]

Curious - I just created a new example 'DB' and stored it in
!PipeDream.User.Library. Extrefs in another document does load this
central file OK.

Whereabouts is your file stored? Can you for instance

*info PipeDream:Library.DB


Stuart
--
Stuart Swales

[Richard Torrens (lists)]

In article <4F9D2A00...@gmail.com>,

Stuart Swales <stuart.swale...@gmail.com> wrote:
> Curious - I just created a new example 'DB' and stored it in
> !PipeDream.User.Library. Extrefs in another document does load this
> central file OK.

> Whereabouts is your file stored? Can you for instance

> *info PipeDream:Library.DB

The setup here is very complicated (and very successful) - but it may
prove difficult to replicate!

A typical file is at:
Server:$.4QD.Manufactur.Parts.Active.80_PCAs.15 4QDCtrl

This isa a manufacti##uring/sales/invoicing/ordering system. There are
over 100 such 'Bills of material' files.

This file in turn calls up (either directly or indirectly:
Server:$.PD.Data.KitsBooked
Server:$.PD.Data.Library.c_PLists
Server:$.PD.Iyo.DB
Server:$.PD.Data.Library.c_Parts
Server:$.PD.Data.Suppliers

In ADFS::harddisc4.$.!Boot.Choices.Boot.PreDesktop I have:

Set Server$Path Share::Lab.
In that computer's Share::Lab.$.!Boot.Choices.Users.Single.Boot.PreDesktop
is correspondingly set
Set Server$Path Share::HD4.


In ADFS::harddisc4.$.!Boot.Choices.Boot.Tasks.!!!User
I have:
Set HomeDir Server:$.PD.<Inet$Hostname>

In ADFS::HardDisc4.$.Utilities.!PipeDream.!Boot
I have:
Set PipeDream$Docs Server:$.PD.Docs.
Set PipeDream$Data Server:$.PD.Data.
Set PipeDream$Local Server:$.PD.Iyo
Set PipeDream$UserPath
Server:$.PD.Data.,Server:$.Resources.Stationery.,<PipeDream$Local>.

This has been working well for years. I have in the past had probelms with
canonicalisations so that Serverpath:: file loaded as Share::Lab.file.