Login ProductsSalesSupportDownloadsAbout |
Home » Technical Support » ElevateDB Technical Support » Support Forums » ElevateDB General » View Thread |
Messages 1 to 4 of 4 total |
Error #403 |
Wed, Mar 25 2020 12:20 PM | Permanent Link |
Mirco Malagoli | Hello,
when I try to create DB like CDCollector example I get the error 403 "ElevateDB Error #403 The database Configuration is read-only and this operation cannot be performed (CREATE TABLE batt)". Tried on different directories and different machines without success. Also, if I deploy the "EDBConfig.EDBCfg" and "EDBDatabase.EDBCat" files from the installer (innoDB), I have "ElevateDB Error # 1000 An error occurred with the Batt cursor (an attempt was made to update a read-only cursor ). ElevateDB manager works and obviously the application with the database created with Manager works well. I don't know what else to watch ... Thanks for your help |
Thu, Mar 26 2020 5:41 AM | Permanent Link |
Roy Lambert NLH Associates Team Elevate | Mirco
Have you inserted the correct information to the engine & session? Roy Lambert |
Thu, Mar 26 2020 6:30 AM | Permanent Link |
Mirco Malagoli | Yes, now I find the way to create the configuration file run time and now I create also the DB (the query do not point to configuration database).
The problem is I cannot deploy the configuration file and catalog from innosetup. If I copy manually it works. Now the only way for me is to create configuration and catalog files run time. I have to deploy a table "country" filled whith all the countries. Roy Lambert wrote: Mirco Have you inserted the correct information to the engine & session? Roy Lambert |
Thu, Mar 26 2020 8:00 AM | Permanent Link |
Roy Lambert NLH Associates Team Elevate | Mirco
>Now the only way for me is to create configuration and catalog files run time. That's the best way to do it. Simply copying the files could mean you have invalid paths. >I have to deploy a table "country" filled whith all the countries. That's not a problem. Create the necessary sql to populate the table, deploy that as a text file. When you app opens check if that file is there, if so load into a stringlist and delete the file then loop down the stringlist executing the sql. To improve performance (but probably not necessary as a one off set up) you could use a parameterised query and just put the data fields into the text file. Another alternative for the whole, which would be a bit more tricky and require sorting out paths, would be to do a backup and restore when you application is first opened. Roy |
This web page was last updated on Tuesday, September 17, 2024 at 04:19 AM | Privacy PolicySite Map © 2024 Elevate Software, Inc. All Rights Reserved Questions or comments ? E-mail us at info@elevatesoft.com |