> But why does MP limit filenames for 32 bit projects to 8 characters?
Anyone
> know?

>>I am not sure if this is a stupid question or not!

>>But why does MP limit filenames for 32 bit projects to 8 characters?

>Anyone

>>know?

>probably an old restriction.
>Nevertheless while almost all apps I've seen work fnie as long file names
>(in clarion), I have seen some cases where the long name caused much wailing
>and gnashing of teeth.  In one case a programmer went over a week unable to
>do as much as compile the app and eventually discovered it came right when
>changing the app to 8 chars.

>A week wasted for him (although not a little relief at being able to
>continue I must say) - and I wonder if having long names is really worth it.

>ie if you adopt the approach that "if it might be broken then it probably
>is" and code accordingly, 99% of the time you'll be wrong (but so what) - 1%
>of the time you'll be right though and save yourself some pain.

>another example is the location of clarion on your hard drive.  Clarion
>defaults to c55. (or Clarion6). I've seen folks install it into cw55, cw60,
>C6 and all other flavours.  But I'm thinking "you know what - they tested
>with C55, all the 3rd parties tested with C55, the one that is likely is to
>cause the _least_ problems is C55 - I'm gonna install into C55 and let some
>other slob figure out that it doesn't work when installed into Clarion55

>>I am particularly intrigued since I am using MP (C6 version) which is for

>32

>>bit apps only anyway and I thought 32 bits could have long filenames.

>The MP Manager app was compiled ages ago, and as far as I know hasn't
>specifically been updated for Clarion 6 yet...(Although I'm not expecting
>too many problems...)

>Cheers
>Bruce

> Geez, you're being incredibly practical here aren't you?! <bg>
>  Actually, I agree 100%.  While there are valid reasons for installing
> Clarion or other software into directories other than the default, I
> think mosttimes it's done just because an individual wants to be
> different and has "their own way" of doing things.  And while I'm slowly
> becoming a convert to the CajunVariableNamingConvention, I still use
> 8-char _file_ names in almost all cases.  The reality is that software
> developers, whether SoftVelocity, Capesoft or Microsoft, simply cannot
> test or foresee every possibility, so the simple solution for any but
> the most demanding situation is to just do the obvious and install stuff
> the way you know it was designed (and for us developers, tyy to design
> the way it is most likely to be used).  And if that just won't work for
> a particular situation, you should: a) don't be surprised when you run
> into problems, and b) be sure to disclose your particular (peculiar)
> setup when seeking support for the problems you run into.

> Ask for trouble, and you will probably get it. ;)

> Ramon
> ----

> >Hi John,

> >>I am not sure if this is a stupid question or not!

> >>But why does MP limit filenames for 32 bit projects to 8 characters?

> >Anyone

> >>know?

> >probably an old restriction.
> >Nevertheless while almost all apps I've seen work fnie as long file names
> >(in clarion), I have seen some cases where the long name caused much
wailing
> >and gnashing of teeth.  In one case a programmer went over a week unable
to
> >do as much as compile the app and eventually discovered it came right
when
> >changing the app to 8 chars.

> >A week wasted for him (although not a little relief at being able to
> >continue I must say) - and I wonder if having long names is really worth
it.

> >ie if you adopt the approach that "if it might be broken then it probably
> >is" and code accordingly, 99% of the time you'll be wrong (but so what) -
1%
> >of the time you'll be right though and save yourself some pain.

> >another example is the location of clarion on your hard drive.  Clarion
> >defaults to c55. (or Clarion6). I've seen folks install it into cw55,
cw60,
> >C6 and all other flavours.  But I'm thinking "you know what - they tested
> >with C55, all the 3rd parties tested with C55, the one that is likely is
to
> >cause the _least_ problems is C55 - I'm gonna install into C55 and let
some
> >other slob figure out that it doesn't work when installed into Clarion55

> >>I am particularly intrigued since I am using MP (C6 version) which is
for

> >32

> >>bit apps only anyway and I thought 32 bits could have long filenames.

> >The MP Manager app was compiled ages ago, and as far as I know hasn't
> >specifically been updated for Clarion 6 yet...(Although I'm not expecting
> >too many problems...)

> >Cheers
> >Bruce