Conversion of large Hypercard Stack to Revolution
support at ahsomme.com
Sun Aug 15 13:54:13 CDT 2010
"wait 0 secs with messages" is better.
The "NULL Hypothesis" is a bit strange but we have encountered many
problems (data disappearing, sorts not working right, filters
filtering too much) all of which were fixed by striping NULLs from
the data before performing the action. Now it is always one of the
first things we do.
I was suggesting removing the NULLs either from each record as it is
imported to the text file - or removing the NULLs from the text file
before using it with Rev. I agree that it would be a bad idea to
removed NULLs from the HC stack directly. Sorry I didn't make that
On Aug 15, 2010, at 11:38 AM, Mark Schonewille wrote:
> "wait 0 secs" really should be "wait 0 secs with messages" to have
> the effect you want.
> Stripping the NULLs is an interesting idea, but there is no way to
> do this inside of HC as far as I know and removing _ALL_ NULLs
> might break the stack.
> Best regards,
> Mark Schonewille
> Economy-x-Talk Consulting and Software Engineering
> Homepage: http://economy-x-talk.com
> Twitter: http://twitter.com/xtalkprogrammer
> KvK: 50277553
> From 15th August, we'll have time for new projects! Be the first in
> line and contact me now!
> Download the Installer Maker plugin for Runtime Revolution at
> On 15 aug 2010, at 17:16, Paul Looney wrote:
>> We've done a lot of large HC to Rev conversions and have run into
>> the same problem.
>> 1. Make sure the original HC stack has been compacted, several times
>> 2. Strip all NULLs before import. These can get into the data if a
>> user has pasted text into the HC fields from Word or some other
>> programs. It appears that Rev removes all data between the NULLs.
>> 3. Don't use Rev cards for a large number of records, it just
>> won't handle the information in this format as well as HC did.
>> Move to a database - or use a text file for the data.
>> 4. Put in some wait states ("wait 0 seconds") in your import
>> routine to let the computer "catch up" and finish processing
>> current information before continuing.
>> 5. Don't try to view the information in a Rev field. This will
>> truncate any information beyond approx 64,000 characters in a
>> line. If you view it in a field and then put the field back into
>> the DB, all of the truncated info will be lost.
>> Paul Looney
> use-revolution mailing list
> use-revolution at lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your
> subscription preferences:
More information about the use-livecode