Can not enter data iin form widget?

Board index

Page 1 of 1 (5 posts)

Tags:

HmpfCBR Registered Member Posts 80 Karma 0 OS	Can not enter data iin form widget? Mon Sep 17, 2012 12:33 pm Hi, I created a small database and now I want to start filling in values via a form. However I can not create a new entry, text fields are greyed out and selections made in the combo box or the calender are not rememberd. The database can be downloaded from https://dl.dropbox.com/u/2658308/secondTry.kexi. What am I doing wrong?
jstaniek Moderator Posts 1027 Karma 2 OS	Re: Can not enter data iin form widget? Mon Sep 17, 2012 1:46 pm Hi, thanks for reporting. What's your Kexi version & distribution version? Best regards, Jarosław Staniek • Qt Certified Specialist • KEXI - Open Source Visual DB Apps Builder • Request a feature or fix for KEXI here • May I help you? Please mention your app's version and OS when asking for help
HmpfCBR Registered Member Posts 80 Karma 0 OS	Re: Can not enter data iin form widget? Mon Sep 17, 2012 2:00 pm jstaniek wrote:Hi, thanks for reporting. What's your Kexi version & distribution version? * Kexi version is 2.5.0-0ubuntu1~precise1~ppa1 * Kubuntu 12.04 with backports for KDE 4.9.1https://launchpad.net/~kubuntu-ppa/+archive/backports
jstaniek Moderator Posts 1027 Karma 2 OS	Re: Can not enter data iin form widget? Mon Sep 17, 2012 9:41 pm Dear HmpfCBR, Nice database. Your input form's data source is a query. Currently Kexi forms based on queries are read-only. This is could change but in 2.7 (please file a wish at bugs.kde.org to support this task). A compromise for now is to base the form directly on a table. Best regards, Jarosław Staniek • Qt Certified Specialist • KEXI - Open Source Visual DB Apps Builder • Request a feature or fix for KEXI here • May I help you? Please mention your app's version and OS when asking for help
HmpfCBR Registered Member Posts 80 Karma 0 OS	Re: Can not enter data iin form widget? Mon Sep 17, 2012 10:05 pm Thanks for the clarification. I'll will enter data in another way for now. Bug tracking at Bug #306960.