processing passwords?

Kenneth Brody kenbrody at spamcop.net
Mon Oct 15 08:50:39 PDT 2012


On 10/13/2012 1:21 PM, Fairlight wrote:
> It's been a long, long time since I've seen it, but I seem to remember cabe
> could ask for passwords for processing tables.  I have a few questions
> about this:
>
> 1) Are there separate processing passwords, or is that just a site password
> on the table, but not in fppath?

Each processing table can have a processing password stored in it.  If the 
processing password and the site password don't match, then filePro will 
require that you provide the processing password before allowing you to 
view/edit the file.

When you create a new processing table, filePro will "attach" the current 
site password to that table.  Starting with 5.0 (I believe), you can change 
the processing password using *cabe's F8/Options screen.

> 2) When using rcabe, is the password the first thing asked for in this
> scenario?

If the processing password matches the site password, *cabe doesn't ask. 
Otherwise, it asks immediately after selecting the processing table you want 
to edit.

> 3) Are any extra questions asked in cabe regarding replacing a password?
> If so, at what point in the flow of cabe?

Not unless you explicitly use the F8/Options screen to change it.

[...]
> As long as I'm at it...is there -any- way to make filePro accept input from
> STDIN on Windows native?  I know pipes exist in Windows, but I have a vague
> memory of them being implemented by temporary files or something similar.

The Windows console API doesn't work on pipes (or "regular" files, either), 
returning an "invalid handle" error if you attempt to do so.  (And there's 
no way to pass anything other than standard ASCII though files or pipes. 
Yes, you can pass ESC and Enter, but you can't pass any F-key, or PageUp, 
for example.)

Try it yourself if you want.  Set PFNEWNTCONSOLE=OFF (a leftover from early 
testing of Windows code, which was never removed), which will cause filePro 
to use stdin/stdout rather CONIN$/CONOUT$.  Everything should work normally 
if you don't redirect input, but filePro will get no input at all if you 
redirect stdin to a file or pipe.

-- 
Kenneth Brody


More information about the Filepro-list mailing list