Removing password from processing table???

[Nancy Palmquist]

Brian,

You make it way to hard.

In the situation below, it is very easy to get the password out. Just 
insert a line at the beginning of the file with ::: (three colons) and
save the file.

It does not matter that you leave the password on line two.  Filepro 
will not care and when the process is opened and resaved it will be gone 
from there.

This really makes it easy to script a solution to this problem.  It is 
just inserting a blank line at the top of the process table.
Nancy
On 4/22/2014 3:57 PM, Brian K. White wrote:
> It's easy IF the table was saved in ascii format.
>
> Basically, open up the table in a plain text editor.
> If everything looks like garbage, as in totally and absolutely random
> with no recognizable text at all, then you need fptech to remove it for you.
>
> If the file looks more or less readable, just not exactly like you are
> used to seeing in cabe ("define processing") then it's easy.
>
> Every line in the file is made up of 3 parts separated by ":"
> label:if:then
> So a line that looks like this in cabe:
>
> @keyn    If: qt eq "0"
>          Then: msgbox "Quantity must not be 0!"
>
> Would look like this in a text editor:
>
> @keyn:qt eq "0":msgbox "Quantity must not be 0!"
>
> A line with no label and no conditional, just a Then: part looks like this:
>
> ::msgbox "Quantity must not be 0!"
>
> With me so far?
>
> OK, EXCEPT the very first line.
> The very first line has an extra, 4th field added to the end, after the
> Then: part. That is the encrypted site password that was in effect at
> the time that table was saved.
>
> Assuming the first line just has comments, it would look like this:
> :'my super table:'brian at aljex.com 20140422:Hrz4Qn62uy
>
> All you have to do is go to the end of that line and backspace over the
> encrypted password and the colon.
>
> The above example line would look like this after:
> :'my super table:'brian at aljex.com 20140422
>
> Save the file and you're done.
>
> I say "text editor" without specifying any particular one or asking what
> OS you are on, because it doesn't matter as long as you do the obvious
> thing. If you are on Windows and use any normal Windows text editor,
> then by *default* it will save the file with DOS line endings, which is
> correct for Windows filepro. If you are on linux or unix and you use any
> linux/unix text editor, it will save the file with unix line endings,
> which is correct for unix filepro. But if you are running filepro on
> linux but pull a process table over to your windows desktop and edit the
> file in Notepad and then send it back to linux, then you get what you
> deserve! :) (don't worry even that is easily fixed)
>

-- 
Nancy Palmquist
Owner
Virtual Software Systems - www.vss3.com
(412) 835-9417