<html><head></head><body>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. <br clear="none">
<br clear="none">
Mike <br clear="none"><br clear="none"><div class="gmail_quote">On Jul 1, 2014, "Brian K. White" <brian@aljex.com> wrote:<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<pre class="k10mail">On 6/28/2014 7:02 PM, Jean-Pierre A. Radley wrote:<br clear="none"></pre><blockquote class="gmail_quote" style="margin: 0pt 0pt 1ex 0.8ex; border-left: 1px solid #729fcf; padding-left: 1ex;">Mike Schwartz propounded (on Sat, Jun 28, 2014 at 09:48:00AM -0500):<br clear="none">|<br clear="none">| >> Fp, in the days of smaller drives, allowed for adding key/data extents to<br clear="none">| the same or different drives. Today with the larger drive capacity, the<br clear="none">| only time one would want to do this is when the file size is nearing the 2GB<br clear="none">| limit on a 32bit OS.<br clear="none">| >><br clear="none">| >> I don't recall exactly what the naming convention is for these extents.<br clear="none">|<br clear="none">| > Yea, please explain what extents is.<br clear="none">| ><br clear="none">| > Thanks, Mike<br clear="none">|<br clear="none">|<br clear="none">| At this point you will have a CUST file that has (roughly) a<br
clear="none">| 1-Gigabyte "key" segment and a 1-Gigabyte "data" segment in it, but the file<br clear="none">| will contain all the data from your original CUST database and it willlook<br clear="none">| and operate exactly like your original CUST file did.<br clear="none">|<br clear="none">| Hope this doesn't confuse you further...<br clear="none"><br clear="none"><br clear="none">Well, it confused me, a bit...<br clear="none"><br clear="none">Mike, you took a database with a key file but a zero-length data file<br clear="none">and moved about half the key files's fields into the data file. If you<br clear="none">reached an OS-imposed 2GB limit in the key file, sure, you would now<br clear="none">reach the 2GB limit on either the key file or the data file,<br clear="none"><br clear="none">But that's not what I ever understood by extents. FilePro can generate<br clear="none">(in addition to key and data) keyx1 &datax1, keyx2 & datax2, keyx3 &<br clear="none">datax3. Instead
of
hitting a 2GB limit on on a single file, you will be<br clear="none">limited to 2GB on any one of the eight files, filePro sees the database<br clear="none">with such extents as having a big virtual concatenated key file (and if<br clear="none">present, a concatenated data file).</blockquote><br clear="none">Exactly.<br clear="none"><br clear="none"><blockquote class="gmail_quote" style="margin: 0pt 0pt 1ex 0.8ex; border-left: 1px solid #729fcf; padding-left: 1ex;">You need to have additional filesystems to exploit this capability.</blockquote><br clear="none">We use extents without any extra filesystems.<br clear="none"><br clear="none">Or are you just saying the automatic creation only works on separate <br clear="none">filesystems?<br clear="none"><br clear="none">It may be that fp will do something a little more automatic like you<br clear="none">described, automatically creating x2 & x3 if x1 exists and there are <br clear="none">extra filesystems listed in PFSOMETHINGOR
OTHER>
I've never tried it. But <br clear="none">we just have one fs and we create the x files ourselves and it works.<br clear="none"><br clear="none">And I believe I was wrong about going up to x9. x3 only.<br clear="none"></blockquote></div><br clear="none">-- Sent with <b><a shape="rect" href="https://play.google.com/store/apps/details?id=com.onegravity.k10.pro2">K-@ Mail</a></b> - the evolution of emailing.</body></html>