On 23/1/02 8:38 pm, Richard D. Miller <[EMAIL PROTECTED]> wrote:
>> Indeed - there is no such limit. Fields can handle as much as you have RAM
>> for, and you can store the data off screen as binary in a custom property.
> How does one transform data into binary? Will it be possible to decode th
Kevin:
> Indeed - there is no such limit. Fields can handle as much as you have RAM
> for, and you can store the data off screen as binary in a custom property.
How does one transform data into binary? Will it be possible to decode the 6
mb of binary data in a few seconds on startup? I looked at
At 10:09 AM -0500 1/22/02, Richard D. Miller wrote:
>I believe the limit per field is 64k, but I'd like to know if that's not the
>case.
>
>If I was to put the 7 mb of data into the custom property of a stack, for
>example, I suppose I could open it as invisible at startup. The question is,
>would
On 22/1/02 2:43 am, John Cuccio <[EMAIL PROTECTED]> wrote:
>> I believe the maximum per field is 64k. That would take very many fields
>> (over 100), and I think too long to read into memory initially.
>
> I thought Rev had not limits. Just how big the hard drive space was.
Indeed - there is no
I believe the limit per field is 64k, but I'd like to know if that's not the
case.
If I was to put the 7 mb of data into the custom property of a stack, for
example, I suppose I could open it as invisible at startup. The question is,
would accessing a particular item in that data be any slower th
At 3:26 PM -0800 1/21/2002, [EMAIL PROTECTED] wrote:
>I'd appreciate suggestions on how to hide a data file. I've got a 7 mb
>primary data file (1650 rows and 130 columns) that's read into memory
>at startup. I'd like to make it more difficult for prying users to get at
>that
>data. Right now it's
Scott:
> Another option is continue using the source file externally but either
> 1) encoding it, such as using base 64 or some other encoding scheme
How would I do that? And would it be possible to un-encode it in, say, 10
seconds when the program is starting up?
> and/or compression
It seems i
Another option is continue using the source file externally but either
1) encoding it, such as using base 64 or some other encoding scheme
and/or compression, or 2) placing the data within a user property of a
stack, and password protecting the stack.
FWIW,
Scott Rossi
Creative Director, Tact
John:
> Do you need to save and access the data file.
I need to read it into memory at startup. I don't need to write to it.
>You could put the data file
> into another rev stack.That way it can not be access by other. Place a field
> on one card then put the data in that field. If the data is t
Do you need to save and access the data file. You could put the data file
into another rev stack.That way it can not be access by other. Place a field
on one card then put the data in that field. If the data is to big maybe
different cards. Then when you need the data call it from your main stack.
I'd appreciate suggestions on how to hide a data file. I've got a 7 mb
primary data file (1650 rows and 130 columns) that's read into memory
at startup. I'd like to make it more difficult for prying users to get at that
data. Right now it's just sitting on the CD. I can't think of any ways to p
11 matches
Mail list logo