"Tim Young [Elevate Software]" <timyoung@elevatesoft.com> wrote:

Tony,

<< Have you tested your instructions for setting up the replication demo on
a PC running Vista? >>

That shouldn't make any difference at all - the path names used are all
right off the root and don't mess with protected areas under Vista that
would cause possible issues.

<< I'm getting errors with almost every script. Mostly, the errors relate to
stores and databases not existing. I admit I don't know much about ElevateDB
but I am following the instructions.>>

What errors are you getting, specifically ?(full message, please)  And how
are you running the scripts, via the ElevateDB Manager ?

--
Tim Young
Elevate Software
www.elevatesoft.com

Tim,

I'm running through the process for the second time after removing all traces of the first attempt. I am using the ElevateDB Manager
and the first problem I strike is with the execution of setupmainoffice.sql which raises this error:

ElevateDB Error #700 An error was found in the statement at line 10 and column 28
(ElevateDB Error #401 The table or view Stores does not exist)

I close the script, reload it and run it again and get a bit further this time:

ElevateDB Error #700 An error was found in the statement at line 30 and column 33
(ElevateDB Error #401 The table or view SalesPerson does not exist)

At this point, I checked the hard drive and there is a folder C:\mainoffice containing a catalog file and a lock file but there are no sub folders.
Under the Stores node in the ElevateDB Manager are listed two stores, Mainsetup & Mainupdates.

If I doubleclick either of the stores, I get a 401 error. I close and reopen the Manager and now I can doubleclick the stores without raising
an error. Two subfolders Setup & Updates have appeared in C:\mainoffice, apparently as a result of restarting the Manager.

Tony.

Tony,

<< I'm running through the process for the second time after removing all
traces of the first attempt. I am using the ElevateDB Manager and the first
problem I strike is with the execution of setupmainoffice.sql which raises
this error:

ElevateDB Error #700 An error was found in the statement at line 10 and
column 28  (ElevateDB Error #401 The table or view Stores does not exist) >>

That most likely means that you're using the 1.x ElevateDB Manager.

--
Tim Young
Elevate Software
www.elevatesoft.com

"Tim Young [Elevate Software]" <timyoung@elevatesoft.com> wrote:

Tony,

<< I'm running through the process for the second time after removing all
traces of the first attempt. I am using the ElevateDB Manager and the first
problem I strike is with the execution of setupmainoffice.sql which raises
this error:

ElevateDB Error #700 An error was found in the statement at line 10 and
column 28  (ElevateDB Error #401 The table or view Stores does not exist) >>

That most likely means that you're using the 1.x ElevateDB Manager.

--
Tim Young
Elevate Software
www.elevatesoft.com



Tim,

Sorry, I took a while to get back, but I checked and I am using Version 2 build 1 for both server and DBManager. I forgot to mention, I am using
Vista 64 bit - could that be relevant?

Tony.

Tony,

<< Sorry, I took a while to get back, but I checked and I am using Version 2
build 1 for both server and DBManager. I forgot to mention, I am using Vista
64 bit - could that be relevant? >>

No.  The Stores table is a virtual table in the system-defined Configuration
database, and only exists in memory.   It's also created automatically by
EDB.

You should also be using Build 2, per the notes at the beginning of the
article:

"This technical article requires the use of ElevateDB 2.0 Build 2 or higher.
There were a couple of minor bugs in the PUBLISH DATABASE functionality for
Build 1 that were resolved in Build 2."

However, that shouldn't affect this issue.  I'm kind of stumped at this
point - the only thing that should cause the Stores table to not exist is
the use of 1.x.  It's present in 2.x in the same manner as the Databases
table - it's always there.

--
Tim Young
Elevate Software
www.elevatesoft.com