home bbs files messages ]

Forums before death by AOL, social media and spammers... "We can't have nice things"

   comp.lang.visual.basic      MS Visual Basic discussions, NOT dot-net      10,840 messages   

[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]

   Message 9,978 of 10,840   
   Joe-Paul to Ralph   
   Re: Query Drops Data   
   27 Mar 06 18:01:46   
   
   From: HarvestWind@comcast.net   
      
   Hi Ralph:   
      
   I have data in one table and each record shows the number of trips taken by   
   each type of vehicle each day, with dispatch times, arrival times, etc.  I   
   want to compare vehicle type 1's "chunk" of data for a given period of time   
   with the same vehicle's "chunk" of data a year ago. (Compare Jan 1, 2005 to   
   Feb 1, 2005 with Jan 1, 2006 to Feb 1, 2006).  So I "append" the frist set   
   of data from table one into table two...then update table two with the info   
   from an SQL getting the corresponding data for the second part of the   
   comparison.  ONce in the second table, I use another SQL to bring the data   
   into a datagrid.  But when I do that, the first time the process runs, the   
   second amount of data does not show up in the grid... I refresh it, but that   
   doesn't change anything.  If put a "msgbox" in the procedures just before   
   the grid is loaded...all data shows...without the "msgbox"...the second half   
   of the data is dropped.   
      
   So...yes, I'm doing some funky things with the data as it is moved to set it   
   up as I need it for the comparison.  Each SQL works right...I've checked   
   each one in Access..and they work... but when I put them together...the   
   second part of the data is dropped.  (If I try to compare over a three year   
   period, the first and second year show up...but the third year is   
   dropped.)..   
      
   So... I'll just have to see if I can work around this some way.   
      
   Thanks   
   JP   
      
      
      
   "Ralph"  wrote in message   
   news:deWdnSkSB56Kv7XZnZ2dnUVZ_vudnZ2d@arkansas.net...   
   >   
   > "Joe-Paul"  wrote in message   
   > news:SdudnShigOOzG7jZnZ2dneKdnZydnZ2d@comcast.com...   
   >> Hi:   
   >>   
   >> I'm running a simple query on an Access Table from VB6.0.  The operator   
   > can   
   >> make several different selections.  Based on their selection, a   
   >> different,   
   >> specific SQL needs to be run.  So, when the operator says... "Do   
   >> it"...the   
   >> click procedure goes to a Function (based on their selection)...the   
   > specific   
   >> function builds the correct SQL and returns it...then it sends that query   
   > to   
   >> the final procedure to run the sql, retrieve the data and put it on my   
   > form.   
   >> When I run the program, it returns the data in the first three fields,   
   >> but   
   >> the fourth field is empty...there is data in that field in the   
   >> table...but   
   >> it is not returned.  I've checked the SQL that is being passed and it is   
   >> being passed correctly.   
   >>   
   >> When I put a "MsgBox SQL" to check out the SQL (after the SQL is   
   >> developed   
   >> and before it is actually run in the final procedure) the SQL is correct   
   > and   
   >> all of the data is printed on the form (that is when the program pauses   
   > and   
   >> waits for the operator to click on the message box).  When there is no   
   > pause   
   >> for a message box, the data is not returned...when them message box is   
   >> there, the data is returned correctly.   
   >>   
   >> CAn anyone tell me what the heck is happening?  And how I might get   
   >> around   
   >> this without having the operator read and close a message box?   
   >>   
   >> Any assistance or suggestion would be helpful.   
   >>   
   >> JP   
   >>   
   >   
   >   
   > I think we need to see some code.   
   >   
   > It is doubtful your SQL is being affected by the msgbox, it has to be   
   > something in how you are attempting to capture or view the value.   
   >   
   > Because the returned values are variants, a msgbox can on occasion affect   
   > displayed results by 'fixing' the value to a specific type. But that is   
   > uncommon and just a wild suggestion on my part.   
   >   
   > Review how you are capturing the values of that last field. Doing anything   
   > cute?   
   >   
   > -ralph   
   >   
   >   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)   

[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]


(c) 1994,  bbs@darkrealms.ca