Databasing with Rev... design considerations

[docmann]

Hello Stephen and thanks for the suggestion. ..
...I was hoping to be able to stay with a native Rev solution if at
all possible, but will give it a whirl if that's the best option.

Appreciate the link :)

-Doc-


On Mon, 31 Jan 2005 01:24:42 -0800, Stephen Barncard
<stephen at barncard.net> wrote:
> Doc, why not just point your mySQL login  to Valentina? You shouldn't
> have to change much at all.
> 
> They have a trial version -- it's an external for Rev...
> http://www.paradigmasoft.com/index.html
> 
> <http://www.paradigmasoft.com/index.html>Paradigmsoft
> 
> 
> >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?
> >
> >-Doc-
>