hello.
i use 4.1.4 unidac to try.
when i need to produce what fields in the table, the unidac (query and table) cannot open even the connection already active in design time
the component error said that the table doesn't exist. but it's work properly when in run time.
i need to assign field to declare the field in grid.
could you help me what's really going on?
i try with another provider (sql server) it work's properly. i found something wrong in sqlite.
please help
thx
UniDAC with sqlite cannot open table at design time
Hello,
Probably you have specified an incorrect path to the DB file. If you have set only the DB name without specifying the exact path, the application tries to find this file in the current working folder (when working in design time, this folder is defined by IDE), and if the file is not found , the new DB file is created with this name, but without tables. Try to specify the exact path to your DB file (X:\MyFolder\MyDB.db3) and check the behaviour in design time once more.
Probably you have specified an incorrect path to the DB file. If you have set only the DB name without specifying the exact path, the application tries to find this file in the current working folder (when working in design time, this folder is defined by IDE), and if the file is not found , the new DB file is created with this name, but without tables. Try to specify the exact path to your DB file (X:\MyFolder\MyDB.db3) and check the behaviour in design time once more.
Hello,
As I wrote above, if a non-existent DB file is specified, an empty DB file will be created over again, and the connection will be set up successfully..
We have checked our components work in design-time one more time and didn't find the problem you have described.
Please send your DB file and an application demonstrating the problem to аlexp*devart*com
As I wrote above, if a non-existent DB file is specified, an empty DB file will be created over again, and the connection will be set up successfully..
We have checked our components work in design-time one more time and didn't find the problem you have described.
Please send your DB file and an application demonstrating the problem to аlexp*devart*com