I whole heartedly agree! I tried to beam a copy of one of my programs to a
customer for evaluation and was thwarted by this restriction. Put it in
flash so I couldn't loose it. Now I can't give it away... Argh!
-Paul
> -----Original Message-----
> From: Richard Hartman [mailto:[EMAIL PROTECTED]]
> Sent: Thursday, July 22, 1999 2:22 PM
> To: '[EMAIL PROTECTED]'; [EMAIL PROTECTED]
> Subject: RE: trouble beaming DB's that are in FLASH
>
>
> My best guess is that they overloaded the meaning
> of the "locked" bit when they added IR. It used
> to mean "don't write or delete this DB", now it
> has the additional meaning of "don't beam this DB".
>
> Since all of the DBs in flash are read-only by
> nature (read: locked), the IR API refuses to
> beam them.
>
> This is, imo, a bug.
>
> --
> -Richard M. Hartman
> [EMAIL PROTECTED]
>
> 186,000 mi./sec ... not just a good idea, it's the LAW!
>
>
> > -----Original Message-----
> > From: Alan Pinstein [mailto:[EMAIL PROTECTED]]
> > Sent: Wednesday, July 21, 1999 2:35 PM
> > To: [EMAIL PROTECTED]
> > Subject: trouble beaming DB's that are in FLASH
> >
> >
> > Is there a reason that this SHOULDN'T work? I haven't been preventing
> > people from doing this, but the beam won't complete successfully, and
> > I notice now that apps in Flash don't show up in the list when I
> > choose 'beam app' from the built-in launcher.
> >
> > Any pointers would be appreciated.
> >
> > Thanks,
> > Alan Pinstein
> > Synergy Solutions, Inc.
> > http://www.synsolutions.com
> > 1-800-210-5293
> >
>
