View Issue Details

IDProjectCategoryView StatusLast Update
0002766JEDI VCL00 JVCL Componentspublic2006-03-30 08:07
ReporteranonymousAssigned Toobones 
PrioritynormalSeverityfeatureReproducibilityalways
Status resolvedResolutionno change required 
Product Version 
Target VersionFixed in Version 
Summary0002766: impossible to input in JvDBGrid if lookup is integer
DescriptionJVCL RC 1:
when you create a lookup field (string) in a dataset, you can input the value directly in the JvDBGrid with the AutoComplete feature, this is a very nice feature that unfortunately does not exist if the lookup field is of type integer? in this case it is impossible to type in the JvDBGrid column and it is obligatory to pick the value by mouse, any workarounds?
TagsNo tags attached.

Activities

obones

2005-04-01 06:02

administrator   ~0006815

The developers of JvDBGrid can't use lookup fields and as such cannot help solving this situation

anonymous

2005-05-17 16:23

viewer   ~0007172

Moreover, input denies tha backspace character so it is imposible to set the value of the field to blank in string fields and others, i see this as very frustrating..

anonymous

2005-05-18 03:52

viewer   ~0007177

I finally managed to use a lookup field with a Paradox database and saw nothing wrong with integer fields.
And there has never been a problem with the backspace character in string fields. So it looks like the bugs are in your app (check your KeyPreview and keys processing events) and not in the component.

Fred

anonymous

2005-05-18 04:24

viewer   ~0007178

I reread your initial post and I think I understood your problem. The Autocomplete feature does not work with integer fields because the PartialKey option of the Locate function works only with string fields. I see no easy solution for that. And that does not mean it is impossible to type in the cell; that just means you cannot look up a partial value (that works fine in my test database because my integer values are 0, 1, 2 and 3).

Fred

Issue History

Date Modified Username Field Change
2005-03-16 13:55 anonymous New Issue
2005-04-01 06:02 obones Note Added: 0006815
2005-05-17 16:23 anonymous Note Added: 0007172
2005-05-18 03:52 anonymous Note Added: 0007177
2005-05-18 04:24 anonymous Note Added: 0007178
2006-03-30 08:07 obones Status new => resolved
2006-03-30 08:07 obones Resolution open => no change required
2006-03-30 08:07 obones Assigned To => obones