Licensing

[Fairlight]

On Windows, you can do:

type >keyx1

The type command will fail with a message to STDERR (or what passes for it
in Windows), but a zero-length file will be created by the redirect anyway.

Barring that sloppy approach, which a client pointed out, I have a
preferred, cleaner methodology:

1) Navigate to the correct directoy in Windows Explorer.
2) File->New->Text Document
3) Name is whatever you need (e.g., keyx1), and accept/click-through the
warning about changing document extension types.

Done.

mark->

On Wed, Jul 02, 2014 at 10:27:05AM -0400, Barry Wiseman thus spoke:
> On 7/1/2014 7:57 PM, Mike Fedkiw wrote:
> > Now I'm confused about the extent thing. If I just go into the directory that has the big key file and rename it how what do I need to do with the data file, rename that too. Also, how would I be able to get the x2 or x3 keys and data created? I'm running Windows server 03 and sorta lost trying to figure out what a separate file system could even be.
> >
> > Mike
> >
> >
> 
> You need a pair of empty (zero-length) files named keyx1 and datax1.  (In *nix this is easy but I'm always scratching my head how to do it in windows.)   Place these in the directory where the big key is, and filePro will automatically start writing new records there instead of to key and data.  From inside filePro the segue from key to keyx1 is invisible.
> 
> There is a facility for this in Expand Files.   At the "How Many Additional Records" prompt, type the word "switch" instead of a number.  However, as Mike Schwartz remembered, this only works when there are actual multiple filesystems, a rarity on today's machines.
> _______________________________________________
> Filepro-list mailing list
> Filepro-list at lists.celestial.com
> Subscribe/Unsubscribe/Subscription Changes
> http://mailman.celestial.com/mailman/listinfo/filepro-list
> 

-- 
Audio panton, cogito singularis.