allowing multiple values causes front end to report error
in [General]
|
From: Jey on 23 Feb 2010 13:08 My database is split into back and front ends. I already have one text field that allows multiple values in a combo box with value list. When I add another multiple value field, the front end gives an error message "the search key was not found in any record". It works ok with the text field as a single value only combo box with value list, it's only when I allow multiple values that it gives the error. What is going on? as I said, there is already a field that allows multiple values, and that one works just fine! As far as I can tell, all the other parameters for the second field are set the same as the first.
From: Allen Browne on 23 Feb 2010 19:16 Try: 1. Delete the linked table from the front end. 2. Compact/repair the front end database. 3. Compact/repair the back end. 4. Open the front end, and link the table again. Let us know how you go. -- Allen Browne - Microsoft MVP. Perth, Western Australia Tips for Access users - http://allenbrowne.com/tips.html Reply to group, rather than allenbrowne at mvps dot org. "Jey" <Jey(a)discussions.microsoft.com> wrote in message news:31B44F2E-6004-42A9-97E0-FAED56710E16(a)microsoft.com... > My database is split into back and front ends. I already have one text > field > that allows multiple values in a combo box with value list. When I add > another multiple value field, the front end gives an error message "the > search key was not found in any record". It works ok with the text field > as a > single value only combo box with value list, it's only when I allow > multiple > values that it gives the error. What is going on? as I said, there is > already > a field that allows multiple values, and that one works just fine! As far > as > I can tell, all the other parameters for the second field are set the same > as > the first.
From: Jey on 3 Mar 2010 13:02 That solved it, thanks! I've set them to compact on close, so hopefully I won't run into that again. "Allen Browne" wrote: > Try: > 1. Delete the linked table from the front end. > 2. Compact/repair the front end database. > 3. Compact/repair the back end. > 4. Open the front end, and link the table again. > > Let us know how you go. > > -- > Allen Browne - Microsoft MVP. Perth, Western Australia > Tips for Access users - http://allenbrowne.com/tips.html > Reply to group, rather than allenbrowne at mvps dot org. > >
From: Gina Whipp on 3 Mar 2010 14:11 Jay, Actually, setting your database to Compact on Close might very well cause other issues. Maybe not *today* but most likely *tomorrow*. It is recommended you uncheck that. -- Gina Whipp 2010 Microsoft MVP (Access) "I feel I have been denied critical, need to know, information!" - Tremors II http://www.regina-whipp.com/index_files/TipList.htm "Jey" <Jey(a)discussions.microsoft.com> wrote in message news:CD0EAD30-D5AC-46D4-AD5B-F7CF955EEE86(a)microsoft.com... That solved it, thanks! I've set them to compact on close, so hopefully I won't run into that again. "Allen Browne" wrote: > Try: > 1. Delete the linked table from the front end. > 2. Compact/repair the front end database. > 3. Compact/repair the back end. > 4. Open the front end, and link the table again. > > Let us know how you go. > > -- > Allen Browne - Microsoft MVP. Perth, Western Australia > Tips for Access users - http://allenbrowne.com/tips.html > Reply to group, rather than allenbrowne at mvps dot org. > >
From: Allen Browne on 3 Mar 2010 20:19
Jay, hopefully you get that message. What Gina is saying to you is important. -- Allen Browne - Microsoft MVP. Perth, Western Australia Tips for Access users - http://allenbrowne.com/tips.html Reply to group, rather than allenbrowne at mvps dot org. "Gina Whipp" <NotInterested(a)InViruses.com> wrote in message news:#zqSZVwuKHA.1796(a)TK2MSFTNGP02.phx.gbl... > Jay, > > Actually, setting your database to Compact on Close might very well cause > other issues. Maybe not *today* but most likely *tomorrow*. It is > recommended you uncheck that. > > -- > Gina Whipp > 2010 Microsoft MVP (Access) > > "I feel I have been denied critical, need to know, information!" - Tremors > II > > http://www.regina-whipp.com/index_files/TipList.htm > > "Jey" <Jey(a)discussions.microsoft.com> wrote in message > news:CD0EAD30-D5AC-46D4-AD5B-F7CF955EEE86(a)microsoft.com... > That solved it, thanks! I've set them to compact on close, so hopefully I > won't run into that again. > > > "Allen Browne" wrote: > >> Try: >> 1. Delete the linked table from the front end. >> 2. Compact/repair the front end database. >> 3. Compact/repair the back end. >> 4. Open the front end, and link the table again. >> >> Let us know how you go. >> >> -- >> Allen Browne - Microsoft MVP. Perth, Western Australia >> Tips for Access users - http://allenbrowne.com/tips.html >> Reply to group, rather than allenbrowne at mvps dot org. >> >> > > |