Databasing with Rev... design considerations

[Sarah Reichelt]

> Now that the mySQL version of my first Rev app has proven to work so
> well (thanks to all who helped me out!), I'm trying to get my head
> wrapped around the process of building a "static" version. By stactic,
> I mean non-server based, for folks who have slow (or no) internet
> connections.
>
> The app requires 4 tables of data, the largest of which has 10 fields
> and around 25,000 records when complete. This app basically functions
> as a searchable lookup table and will not be editable by the user, nor
> do I wish for the user to have access to the data other than from
> within my application.
>
> The simplest method I can think of is to somehow store and use CSV
> data files (exported from the mySQL version) from a separate stack,
> but I unfortunately don't have a clue as to how to set something like
> this up.
>
> What might be the best approach here?
>
Valentina would work, but first I suggest you try an internal method as 
you suggest.
Make a data stack, either as a separate stack file or as a sub-stack of 
your interface stack.
You have 4 tables, so give it 4 fields and stick your data in them.

If it is all comma separated, then it's easy to extract various items 
for display in the interface. Use the filter command to find certain 
records, taking care to filter a copy of the data, not the original as 
filter removes non-matching lines e.g.
put fld "Table1" of stack "Data" into tData
filter tData with "*" & tWordToFind & "*"
put tData into fld "FoundRecords"

When you build the app, if the data stack is a sub-stack, make sure you 
check the box that says, save sub-stacks as separate files. This means 
they can be written to and saved again.

Cheers,
Sarah
sarahr at genesearch.com.au
http://www.troz.net/Rev/