Erwin Craps - IT Helps
Erwin.Craps at ithelps.be
Fri Mar 4 03:03:18 CST 2005
I'm not sure I understand the problem fully, but I believe to recognise an issue I struggled with when running in a Access Runtime with listboxes. This was the case with listboxes rowsource property that was set from VBA code. Sometimes, with some users it was blanc whatever I did... Only in the Runtime version, not in Full Access. The problem lies in the rowsource property. Because I build the SQL string in VBA code to set it when selecting stuff, I used to leave the rowsource property empty. By dooing this the runtime does not know how to build the colomns (fields) of the listbox. It is posible this was only with an unbound control, I don't know that. The solution is to always set the rowsource property with a correct SQL string so the runtime knows when opening the form how much fields there are. I also tend to set my sql string criteria to "Somefield is null" so I was sure no data was displayed when first opening the form. This is true for A2K runtime, don't know for others, but since then I always program it this way. Erwin -----Original Message----- From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Charlotte Foust Sent: Thursday, March 03, 2005 11:52 PM To: Access Developers discussion and problem solving Subject: RE: [AccessD] AXP Combobox Shows blank formatted date column Eek! Did I remember to mention that the Record number combobox is unbound? It is merely used to select a report for viewing in the subforms. Charlotte Foust -----Original Message----- From: Mark A Matte [mailto:markamatte at hotmail.com] Sent: Thursday, March 03, 2005 2:29 PM To: accessd at databaseadvisors.com Subject: RE: [AccessD] AXP Combobox Shows blank formatted date column Charlotte, I also remember this...but it has been some years...the part I do remember is that my client was using the A2k runtime...not sure of the OS. I'm not sure how the ACCESSD archives are stored...but I'm pretty sure I would have asked this list for help ( and got it)...and it would have been between Nov 2000 and May 2001. Other that that...later tonight I can pull up the app I sent him and look for anything 'different or odd' that I did to the date fields. Thanks, Mark >From: "Charlotte Foust" <cfoust at infostatsystems.com> >Reply-To: Access Developers discussion and problem >solving<accessd at databaseadvisors.com> >To: "Access Developers discussion and problem >solving"<accessd at databaseadvisors.com> >Subject: RE: [AccessD] AXP Combobox Shows blank formatted date column >Date: Thu, 3 Mar 2005 14:02:34 -0800 > >No, if it were the runtime installation (which is AXP SP3, BTW), we'd >have problems on all the installations at that client. It's only >turning up on some of the Win2k machines, not all. Even then, it >doesn't make sense that it would display properly when you selected a >well from the combobox on the form but not when you selected a well >from another form and passed the value back, since that calls exactly >the same AfterUpdate event for the Well combobox that making a direct >selection calls. Furthermore, it ONLY breaks after opening the second >form and choosing a well from there. We can't reproduce it in our >office at all, but one of our owners saw it in action at the client >location. > >Charlotte Foust > > >-----Original Message----- >From: dmcafee at pacbell.net [mailto:dmcafee at pacbell.net] >Sent: Thursday, March 03, 2005 1:54 PM >To: Access Developers discussion and problem solving >Subject: RE: [AccessD] AXP Combobox Shows blank formatted date column > > >Something to do with the runtime maybe? Are you testing with a true >runtime or using the /runtime parameter in the command line when >testing on your end? > > >D > >-----Original Message----- >From: accessd-bounces at databaseadvisors.com >[mailto:accessd-bounces at databaseadvisors.com]On Behalf Of Charlotte >Foust >Sent: Thursday, March 03, 2005 1:45 PM >To: Access Developers discussion and problem solving >Subject: RE: [AccessD] AXP Combobox Shows blank formatted date column > > >We're trying to find out *why* it's happening so we can prevent it, and >the form is shared with the Access version, so an sproc or view is out >of the question. The client is in Oklahoma and using a runtime >executable, so there isn't any printing to the immediate window. The >fact that the dates appear if we remove the Format function from the >rowsource strongly suggests that the dates are there but that something >is interfering in rendering them. > >Charlotte Foust > > >-----Original Message----- >From: dmcafee at pacbell.net [mailto:dmcafee at pacbell.net] >Sent: Thursday, March 03, 2005 11:15 AM >To: Access Developers discussion and problem solving >Cc: Steve White >Subject: RE: [AccessD] AXP Combobox Shows blank formatted date column > > >Have you printed to the immediate window to see if the value is >actually in the combo (just not displaying)? > >What about changing the resource to a view or sproc that formats the >number for you? > >D > >-----Original Message----- >From: accessd-bounces at databaseadvisors.com >[mailto:accessd-bounces at databaseadvisors.com]On Behalf Of Charlotte >Foust >Sent: Thursday, March 03, 2005 11:04 AM >To: AccessD at databaseadvisors.com >Cc: Steve White >Subject: [AccessD] AXP Combobox Shows blank formatted date column > > >We have a client installation where certain machines running Windows >2000 are seeing an odd behavior in a combobox that displays two >columns, a report number and a medium formatted date. We have not been >able to reproduce the behavior here even on Win2k, so I need some >ideas. The back end is SQL Server 2000 and the combobox has this for a >rowsource: > >SELECT ReportNo, ReportNo as [Number], Format(ReportDate, "dd-mmm-yy") >FROM DailyDrillHdr WHERE >((DailyDrillHdr.WellID=[Forms]![frmDailyRpt]![cboWellID])) Order by >ReportNo desc; > >This works fine when the form opens and a WellID is selected. It >breaks when the user brings up a popup form that allows them to select >a different WellID and hand that back to the initial form. The initial >form obligingly changes the WellID in its Well combobox, which >repopulates the subform, and it specifically requeries the report >number combobox in the AfterUpdate event of the WellID combobox. > >At this point, however, on those problem machines, the date column of >the report number combo is blank and it doesn't show dates again until >the form is closed and reopened. The combobox is being requeried, >because the correct report numbers do show up in it, but not the dates >associated with them. The really odd part is that if you take the >formatting out of the combobox rowsource, the dates show up every time. > > >Has anyone else seen something like this? I know I have, but it's been >years ago and I can't remember what caused it! > >Charlotte Foust >Infostat Systems, Inc. >-- >AccessD mailing list >AccessD at databaseadvisors.com >http://databaseadvisors.com/mailman/listinfo/accessd >Website: http://www.databaseadvisors.com > >-- >AccessD mailing list >AccessD at databaseadvisors.com >http://databaseadvisors.com/mailman/listinfo/accessd >Website: http://www.databaseadvisors.com >-- >AccessD mailing list >AccessD at databaseadvisors.com >http://databaseadvisors.com/mailman/listinfo/accessd >Website: http://www.databaseadvisors.com > >-- >AccessD mailing list >AccessD at databaseadvisors.com >http://databaseadvisors.com/mailman/listinfo/accessd >Website: http://www.databaseadvisors.com >-- >AccessD mailing list >AccessD at databaseadvisors.com >http://databaseadvisors.com/mailman/listinfo/accessd >Website: http://www.databaseadvisors.com -- AccessD mailing list AccessD at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/accessd Website: http://www.databaseadvisors.com -- AccessD mailing list AccessD at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/accessd Website: http://www.databaseadvisors.com