This actually doesn't have anything to do w/ VFP, but since the problem *may* cross over to it I didn't flag this as [NF]... forgive me if I'm wrong...
I have a MS Access query that gets run for detail lines on a sub-form in an Access Form. It's the classic orders/orderdetails i.e. parent/child relationship sort of thing. Users can select inventory items to include on an Order, then the qty, price, etc - the usual stuff. The query populates the combobox controlsource. User starts typing in the combobox, the list is supposed to go to that part of the itmes in the list, they keep typing it keeps getting closer to what they are looking for - usual combobox stuff. I've recently changed the way this thing works to deal with a new bike we have come out with. This is the "tikit_built" logical fields seen in the query below. The problem is this: sometimes the list is incomplete - it stops at parts beginning with the letter 'S', or 'U', or some place other than being complete. I've never seen it truncate before the letter 'R'. If I run the query in Access, I always get the complete list. If I run this code in PostgreSQL on the backend - the list is always complete. To complicate matters, it doesn't always truncate the combobox list - about 75% of the time it is just fine. Usually exiting out of the Access app and coming back in (*usually*) will correct the problem, but not always. For reference, here's the code: SELECT DISTINCT Parts.partid, PartTypes.typedescription, Parts.partdesc, Parts.unitprice, Parts.discontinued, Parts.unitcost, Parts.currentcount, Parts.specialorderitem, PartTypes.parenttype, PartTypes.parttypeid, Parts.tikit_built FROM PartTypes INNER JOIN (Parts INNER JOIN Parts_PartTypes_CT ON Parts.partid = Parts_PartTypes_CT.partid) ON PartTypes.parttypeid = Parts_PartTypes_CT.parttypeid WHERE (((Parts.discontinued)=False) AND ((Parts.specialorderitem)=False) AND ((PartTypes.parenttype) Is Null) AND ( Parts.partid <= 200003 or (Parts.tikit_built=TRUE AND Parts.currentcount > 0)) ) ORDER BY PartTypes.typedescription, Parts.partdesc ; My gut tells me that this is a timing issue... the control just can't keep up with running the query in the background to populate the combobox... I've tried tweeking the settings for the ODBC calls from the machine to PostgreSQL but that doesn't seem to have any effect. I've written the calls to postgres log files but those aren't very informative to my eyes... I am stumped and frustrated and would welcome any ideas that might solve this... otherwise I may have to come up with a completely new way of dealing with these new types of bikes and that would be a very hard sell to my users.... Matthew S. Jarvis IT Manager Bike Friday - "Performance that Packs." www.bikefriday.com 541/687-0487 x140 [EMAIL PROTECTED] _______________________________________________ Post Messages to: ProFox@leafe.com Subscription Maintenance: http://leafe.com/mailman/listinfo/profox OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech ** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
