Odd Errors returned

Chuck Neal chuck at mediamacros.com
Wed Apr 13 18:00:23 CDT 2005


Ah.  Sorry.  The last version of 1.  My mistake. This is a large project 
and I do not want to recode it this late in the process for 2.0. ;)


-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


Ruslan Zasukhin wrote:
> On 4/14/05 12:10 AM, "Chuck Neal" <chuck at mediamacros.com> wrote:
> 
> Hi Chuck,
> 
> Do you use 1.x or 2.0 ?
> 
> 
>>I have a project that has an export feature where it clones records to a
>>new temp database.  It basically loops through the records and copies
>>the content out and fills it back in the new file.  For images I import
>>into a Director cast member then put it back in the second DB.  Its not
>>running out of RAM but on certain larger sets of records I start getting
>>errors over and over.  This is one query that works for the first 30 or
>>so but after starts this...
>>
>>UPDATE ids SET max_record = 275 WHERE table_name = 'technique_image'
>>
>>-39 No error
>>
>>Error is -39 but it says no error.
>>
>>
>>Another in the loop is this..
>>
>>UPDATE ids SET max_record = 278 WHERE table_name = 'technique_image'
>>This gives me an error 301
>>
>>Any idea why it starts?  Is it just bad to do too many DB changes in loops?
> 
> 


More information about the Valentina mailing list