Support Forums - View Thread

View Thread

The following is the text of the current message along with any replies.

Messages 1 to 5 of 5 total

Wed, Apr 2 2008 12:07 AM	Permanent Link
"Tomas"	I'm using EDB. My app calls ALTER DATABASE 'XXX' PATH.. whenever app is started. It's ok but after i try connect to it with EDBManager. There's always Error #100.(EDBMgr and app) If i have catalog file without config file, HOW can i connect to the database? Do i have to keep catalog file and config file(session)? What should i do?
Wed, Apr 2 2008 2:36 AM	Permanent Link
Roy Lambert NLH Associates Team Elevate	Tomas Have you altered the Engine ConfigPath or the Session.LocalConfigPath (if Engine.UseLocalSessionEngineSettings is true)? Roy Lambert [Team Elevate]
Wed, Apr 2 2008 2:13 PM	Permanent Link
Tim Young [Elevate Software] Elevate Software, Inc. timyoung@elevatesoft.com	Tomas, << It's ok but after i try connect to it with EDBManager. There's always Error #100.(EDBMgr and app) >> 1) Make sure that you're using the same version of ElevateDB for your application and the ElevateDB Manager. Do not mix and match versions (you can mix and match builds, but not versions). 2) Make sure that the ElevateDB Manager session and your application are both using the same configuration file. << If i have catalog file without config file, HOW can i connect to the database? >> Just use the CREATE DATABASE statement to create a reference to the existing database catalog/tables in the current configuration file. -- Tim Young Elevate Software www.elevatesoft.com
Thu, Apr 3 2008 7:42 PM	Permanent Link
"Tomas"	The problem was from EDBMgr version mismatch. Why does each of minor version use different format? It looks like if my app use small version number, I have to keep the version of EDBMgr to modifiy the data of the app. "Tim Young [Elevate Software]" <timyoung@elevatesoft.com> wrote in message news:5AA7E2A0-662B-4122-B62B-D8A3A725C6B4@news.elevatesoft.com... > Tomas, > > << It's ok but after i try connect to it with EDBManager. There's always > Error #100.(EDBMgr and app) >> > > 1) Make sure that you're using the same version of ElevateDB for your > application and the ElevateDB Manager. Do not mix and match versions (you > can mix and match builds, but not versions). > > 2) Make sure that the ElevateDB Manager session and your application are > both using the same configuration file. > > << If i have catalog file without config file, HOW can i connect to the > database? >> > > Just use the CREATE DATABASE statement to create a reference to the > existing database catalog/tables in the current configuration file. > > -- > Tim Young > Elevate Software > www.elevatesoft.com >
Fri, Apr 4 2008 2:54 PM	Permanent Link
Tim Young [Elevate Software] Elevate Software, Inc. timyoung@elevatesoft.com	Tomas, << Why does each of minor version use different format? >> It could possibly, which is the reason for the version number check. And it is only an issue if you modify the database catalog by creating, altering, or dropping database objects via DDL statements. If the database catalog is not modified, then you could use a version 1.04 database catalog with a 1.09 application and 1.08 EDB Manager with no problems. However, once the database catalog is modified using 1.09, then all applications and the EDB Manager must use 1.09 to gain access to the database catalog without an error. << It looks like if my app use small version number, I have to keep the version of EDBMgr to modifiy the data of the app. >> Yes, that is the case. -- Tim Young Elevate Software www.elevatesoft.com