Limit To List - table showing incorrect data p-rat <osupratt[ at ]yahoo.com> 11/18/2008 5:36:50 PM I have a combobox to where if a value isn't listed you can add it. On my form this works correctly and when the record is pulled or when looking in the underlying table the data isn't correct. Would anyone know why this might be? The values are pulling from a query and the query looks good. This combobox also autofills the next text box on the form. Example: If I look for location "Dallas" on the list and it's there it will autofill the next box with a number assigned to Dallas. If I look for a location and it isn't there I can type in a location and when hitting tab it will pop up a form that I enter the new location again and then a number assigned to this new location. When hitting 'ok' it will ask 'Do you want to add this value to the list?". This seems to work correctly. In the underlying location table it looks good. In the underlying query for this location table it looks good. When I look at the table for the data collection of the form (linked table to SQL Server) the location are wrong. They are numbers instead of text. It looks as though they might be the row or something of the location in a table. Do I have something set to the wrong column or ???

Re: Limit To List - table showing incorrect data John W. Vinson <jvinson[ at ]STOP_SPAM.WysardOfInfo.com> 11/18/2008 6:26:21 PM On Tue, 18 Nov 2008 09:36:50 -0800 (PST), p-rat <osupratt[ at ]yahoo.com> wrote: [Quoted Text] >In the underlying location table it looks good. In the underlying >query for this location table it looks good. When I look at the table >for the data collection of the form (linked table to SQL Server) the >location are wrong. They are numbers instead of text. It looks as >though they might be the row or something of the location in a table. >Do I have something set to the wrong column or ??? My guess is that you're yet another victim of Microsoft's "Lookup Field" abomination. This causes confusion because what's stored in the table is a number, but what you *see* is the text value (from the lookup table). Is this in fact a Lookup Field in your table definition? -- John W. Vinson [MVP]

Re: Limit To List - table showing incorrect data p-rat <osupratt[ at ]yahoo.com> 11/18/2008 6:55:21 PM Yes. How is this solved? I can't figure it out. Thanks for your reply. On Nov 18, 12:26 pm, John W. Vinson <jvinson[ at ]STOP_SPAM.WysardOfInfo.com> wrote: [Quoted Text] > On Tue, 18 Nov 2008 09:36:50 -0800 (PST), p-rat <osupr...[ at ]yahoo.com> wrote: > >In the underlying location table it looks good. In the underlying > >query for this location table it looks good. When I look at the table > >for the data collection of the form (linked table to SQL Server) the > >location are wrong. They are numbers instead of text. It looks as > >though they might be the row or something of the location in a table. > >Do I have something set to the wrong column or ??? > > My guess is that you're yet another victim of Microsoft's "Lookup Field" > abomination. This causes confusion because what's stored in the table is a > number, but what you *see* is the text value (from the lookup table). > > Is this in fact a Lookup Field in your table definition? > -- > >              John W. Vinson [MVP]

Re: Limit To List - table showing incorrect data p-rat <osupratt[ at ]yahoo.com> 11/18/2008 7:26:37 PM OK. After reading your message I was able to search through some posts and found that I needed to change my 'Bound' property to column(1). This fixed one of my problems. It is now storing the correct value for the Location in my database. The autofill value that gets sent to an unbound text box is not storing the correct value. It stores 0. Any clues on this issue? On Nov 18, 12:55 pm, p-rat <osupr...[ at ]yahoo.com> wrote: [Quoted Text] > Yes. How is this solved? I can't figure it out. Thanks for your reply. > > On Nov 18, 12:26 pm, John W. Vinson > > > > <jvinson[ at ]STOP_SPAM.WysardOfInfo.com> wrote: > > On Tue, 18 Nov 2008 09:36:50 -0800 (PST), p-rat <osupr...[ at ]yahoo.com> wrote: > > >In the underlying location table it looks good. In the underlying > > >query for this location table it looks good. When I look at the table > > >for the data collection of the form (linked table to SQL Server) the > > >location are wrong. They are numbers instead of text. It looks as > > >though they might be the row or something of the location in a table. > > >Do I have something set to the wrong column or ??? > > > My guess is that you're yet another victim of Microsoft's "Lookup Field" > > abomination. This causes confusion because what's stored in the table is a > > number, but what you *see* is the text value (from the lookup table). > > > Is this in fact a Lookup Field in your table definition? > > -- > > >              John W. Vinson [MVP]- Hide quoted text - > > - Show quoted text -

Re: Limit To List - table showing incorrect data p-rat <osupratt[ at ]yahoo.com> 11/18/2008 8:03:42 PM I got it. I appreciate your help. Just sometimes getting me pointed in the correct direction helps. Thanks allot. On Nov 18, 1:26 pm, p-rat <osupr...[ at ]yahoo.com> wrote: [Quoted Text] > OK. After reading your message I was able to search through some posts > and found that I needed to change my 'Bound' property to column(1). > This fixed one of my problems. It is now storing the correct value for > the Location in my database. The autofill value that gets sent to an > unbound text box is not storing the correct value. It stores 0. Any > clues on this issue? > > On Nov 18, 12:55 pm, p-rat <osupr...[ at ]yahoo.com> wrote: > > > > > Yes. How is this solved? I can't figure it out. Thanks for your reply. > > > On Nov 18, 12:26 pm, John W. Vinson > > > <jvinson[ at ]STOP_SPAM.WysardOfInfo.com> wrote: > > > On Tue, 18 Nov 2008 09:36:50 -0800 (PST), p-rat <osupr...[ at ]yahoo.com> wrote: > > > >In the underlying location table it looks good. In the underlying > > > >query for this location table it looks good. When I look at the table > > > >for the data collection of the form (linked table to SQL Server) the > > > >location are wrong. They are numbers instead of text. It looks as > > > >though they might be the row or something of the location in a table.. > > > >Do I have something set to the wrong column or ??? > > > > My guess is that you're yet another victim of Microsoft's "Lookup Field" > > > abomination. This causes confusion because what's stored in the table is a > > > number, but what you *see* is the text value (from the lookup table). > > > > Is this in fact a Lookup Field in your table definition? > > > -- > > > >              John W. Vinson [MVP]- Hide quoted text - > > > - Show quoted text -- Hide quoted text - > > - Show quoted text -

Re: Limit To List - table showing incorrect data John W. Vinson <jvinson[ at ]STOP_SPAM.WysardOfInfo.com> 11/18/2008 8:05:15 PM On Tue, 18 Nov 2008 11:26:37 -0800 (PST), p-rat <osupratt[ at ]yahoo.com> wrote: [Quoted Text] >OK. After reading your message I was able to search through some posts >and found that I needed to change my 'Bound' property to column(1). >This fixed one of my problems. It is now storing the correct value for >the Location in my database. The autofill value that gets sent to an >unbound text box is not storing the correct value. It stores 0. Any >clues on this issue? Not without knowing how you did the "sending". Do note that the Column() property is zero based, so =combobox.Column(1) is actually the second field in the combo's rowsource - there is an infuriating discrepancy between the convention for the Bound Column property (1-based) and the Column property (0-based). -- John W. Vinson [MVP]