wrote:
> Does/did the workstation in question have an unusually long PATH statment
> that is getting truncated? The path statement length limit for XP was 1024
> characters,
> 2048 in SP2...don't recall for SP3.
> Is the full PATH stamtent displayed when you issue "PATH" at a command
> prompt?
>
> --
> John Strano - Sybase Technology Evangelist
>
> blog:http://powerbuilder.johnstrano.com/
>
> "mike" <mg.enigm...@gmail.com> wrote in message
>
> news:6144f97f-ea33-4677-bc06-42a6c3d3cbee@r18g2000yqd.googlegroups.com...
>
>
>
>
>
>
> > > On Aug 13, 8:02 am, Wheeley <whee...@ix.netcom.com> wrote:
>
> > > > On Wed, 12 Aug 2009 08:03:01 -0700 (PDT), mike <mg.enigm...@gmail.com>
> > > > wrote:
>
> > > > >Sorry I skipped Paul question.
> > > > >it's from the IDE
>
> > > > The problem with bitmaps is powerbuilder uses the Windows search path
> > > > to find them. The Windows search path is as follows:
>
> > > > The active directory
> > > > The Windows directory
> > > > The Windows system directory
> > > > All directories in the PATH environment variable
>
> > > > From WITHIN the ide, the active directory can change depending what
> > > > you do. The active directory on ide startup is typically the active
> > > > target's directory. But as stated before this can change by simply
> > > > doing an object export from a pb, a getfileopenname command while
> > > > running your application, plus other things.
>
> > > > Obvously you don't want to place your bitmaps in the Windows or
> > > > Windows system directories so that leaves something on the PATH
> > > > variable.
>
> > > > From my experience, I always place my own bitmaps in the
> > > > sybase\shared\powerbuilder directory and it always work for both
> > > > development and at runtime from within the ide. Give that a try.
>
> > > > Hope this helps
> > > > Wheeley
>
> > > Application specific files in sybase's shared folder? Ew...
>
> > > The search path also contains the folder that the exe was run from.
> > > But when running your application from the IDE, this is %ProgramFiles%
> > > \Sybase\Powerbuilder <version>. which isn't very useful.
>
> > > You could also make sure your target's main folder is in your
> > > process's own path environment variable when run from the IDE.
> > > Something like this should work somewhere in your applications startup
> > > code;
>
> > > type prototypes
> > > function boolean SetEnvironmentVariable(string as_name, string
> > > as_value) library "kernel32.dll" alias for "SetEnvironmentVariableW"
> > > end prototypes
>
> > > if handle(getapplication())=0 then
> > > contextkeyword lck
> > > classdefinition lcd
> > > application la
> > > string lsa_path_values[], ls_application_folder
>
> > > la=getapplication()
> > > lcd=la.classdefinition
> > > ls_application_folder = left(lcd.libraryname,lastpos
> > > (lcd.libraryname,'\'))
> > > la.GetContextService("ContextKeyword", lck)
> > > lck.GetContextKeywords("PATH", lsa_path_values)
> > > if pos(lsa_path_values[1], ls_application_folder)<=0 then
> > > SetEnvironmentVariable("PATH", ls_application_folder+ ";" +
> > > lsa_path_values[1])
> > > end if
>
>
> > hey guy's ,
> > this is great info.
>
> > But still, it does not explain why on the same window only one image
> > button do not work and the others (on the same window) works. We have
> > a total of 6 image button and only one of them don't appear (the
> > image) at runtime (from the IDE). But again in design it is ok, it
> > does appear. Only when we run the app from the IDE then "pow" it is
> > gone but the others at ok, we see the images on the others.
>
> > We even tried replacing his PBL from another developper. Still the
> > same problem for that only developper. Other developpers are ok. So it
> > might be his PC or glitch somewhere. We don't compile from his machine
> > for the EXE :-) so it's not a big deal, but we are sure "intrigue" by
> > this.
>
> > thank you all for the help... allways can count on you guys
>
>
> we took your previous recommandation and seems to work. We moved the
> image to the directory where the PB.exe is (c:\program files\sybase
> \powerbuilder) and worked. So we are onto something.
>
>
Hi John,
the PATH is fine. It's about 580 long.
|