Re: How can a preview copy of StoryServer  be obtained?

Greetings to all my high functioning EccoPro pals and 'hey r6' !  You all may remember I posted alot about a thing called "EverEcco" maybe 4 or 5 years ago (??) but I was also battling cancer at the time.  Well, I didn't die afterall. I have been feeling good since summer and lurking the Ecco boards these past several months ... just about the time StoryServer was announced. 

I am excited about StoryServer (SS) --- I was ready to jump to Airtable 6 months ago for a new project.  Do you know Airtable?  It is "Ecco in the cloud with a modern set of tools".  Thing is (a) you lease for the privilege to access your data; (b) what happens when Airtable has been hacked?;  (c) what happens to all your data and customizations when Airtable folds or the west coast sinks in to the ocean?

So ya, when SS was announced I got excited enough to think about manually porting over  everything that DDE does not export.  Why?  I have had too many scary data bug-a-boos with Ecco over the years. As much as I love Ecco - and I do - it is just too unstable - for me anyway - to trust to my last hurrah in life ... "thoseCwords ... a podcast and website for people dealing with cancer and other Cwords".  

So ya, SS has me excited.

To r6 and anyone else w/ complex (and old) databases:  I have been reading your posts for a long time and understand that you have a complex custom setup and I understand why it would be cumbersome to manually port everything (and a 'dynamic everything' at that) over to a new program.   

My question is .... how do you keep EccoPro (+EE) from screwing up your precious data?  And especially with all the custom rules and routines?  Does your database(s) not cause your heart to skip a beat upon occasion?  Mine sure do.

As one example - a couple years ago I got fatal-sounding errors on searches (I forget the exact words) but basically Ecco was saying there was a non-recoverable error.  No I I was not hitting any limits and luckily Ecco didn't crash and burn.  JS helped me out ... it was something in the tree that had gone astray.  There is a way to export the tree but man, my tree is long and finding the error was not an easy task.  I do not want to go through that again but after 2 or so years the error message is back.  Hence ... "StoryServer to the rescue" (!!??!!)

Again r6 - and everyone else with complex &/or old databases: 
Do you get scary error messages??  ... to the point where you would look to an Airtable or StoryServer as a way to gain Ecco functionality without the fear of data corruption?  Or do you not get error messages?  Or are you simply that brave?

Talk to me folks :-)

-Mark/MD/airchecklover/stage IV cancer survivor/EverEcco guy/StoryServer hopeful