301 Errors

[Chuck Neal]

Well the problem is that this is a new database.  I create the new database
and add the paired data to it but reading records, getting the info via a
list, then writing them to the new database.  This works fine for smaller
chunks of data but the larger ones seem to corrupt it every single time.
The original database is not effected, its just the new one that seems to
give me problems.  What causes this in the first place?  Is there a command,
or common event that makes this happen that I should avoid?

I was able to export a small group just now with no problems, yet others
fail every single time with a 301 error.  I can't always predict the size or
content of the data the user will have so how can I safeguard against this
happening at runtime?

-Chuck
--------------------------
Chuck Neal
CEO, MediaMacros, Inc.
chuck at mediamacros.com
http://www.mediamacros.com
--------------------------
Check out the Developers Mall 
Your one stop shop for all your Director Xtra Needs
http://www.mediamacros.net/customer


-----Original Message-----
From: valentina-bounces at lists.macserve.net
[mailto:valentina-bounces at lists.macserve.net] On Behalf Of Ruslan Zasukhin
Sent: Tuesday, October 19, 2004 12:51 PM
To: valentina at lists.macserve.net
Subject: Re: 301 Errors


On 10/19/04 6:46 PM, "Chuck Neal" <chuck at mediamacros.com> wrote:

> I have a setup where a user has a master database, and then they can 
> choose to export a portion of this to a new database.  The code is set 
> up to spider through the selections to pull in all the options needed 
> from each table, and relink with the new id numbers.
> 
> The first pass worked fine, but as I started exporting larger sets of 
> data it began to show problems.  I was getting 301 errors every time 
> in the same place.  I found the function that appeared to be the 
> problem and reworked it so that it was not making as many database 
> calls, then ran it again.  This time it gave the same error somewhere 
> else.  It seems that its not the SQL so much as the number of 
> sequential calls.  I have tried flushing the database, etc, but no 
> luck.  It still regularly corrupts the file when I export a lot of 
> data this way.
> 
> Anyone had similar problems?  I found a post about setting the size to 
> 32 bytes instead of 1-4 but that had no effect.

Hi Chuck,

    kFBL_DataFileError            = 301,

This means you have corruption.

You need XML dump / load


-- 
Best regards,
Ruslan Zasukhin      [ I feel the need...the need for speed ]
-------------------------------------------------------------
e-mail: ruslan at paradigmasoft.com
web: http://www.paradigmasoft.com

To subscribe to the Valentina mail list go to:
http://lists.macserve.net/mailman/listinfo/valentina
-------------------------------------------------------------

_______________________________________________
Valentina mailing list
Valentina at lists.macserve.net
http://lists.macserve.net/mailman/listinfo/valentina