mySQL database query

[James Spencer]

I think if I saw any one of these variations on "correct data" I  
could figure out how to do the others but my instinctive answer would  
be the previous record (or the new first record if the first record  
were the one deleted.)  My first go at this isn't fussy; I just  
"know" that leaving a record displayed that isn't in the database any  
more is probably "wrong".  (I haven't even looked at sorting the  
records yet.)

Thanks much for helping this newby to dbs.

Spence

James P. Spencer
Rochester, MN

jspencer78 at charter.net

"Badges??  We don't need no stinkin badges!"

On Jul 5, 2005, at 10:14 PM, Dan Shafer wrote:

> James....
>
> What constitutes "the correct data" to display after the deletion?  
> Empty fields? Previous record? Next record? In some sort of sort  
> sequence?
>
> Once you can define that, I think writing a bit of Transcript to  
> give you what you want is pretty easy but there's no sort of de  
> facto rule about what the display should show after a record is  
> deleted.
>
> Dan
>
> On Jul 5, 2005, at 6:59 PM, James Spencer wrote:
>
>
>> As long as we are talking about mySQL, is there a way to  
>> programatically refresh a database query?  I have a master/detail  
>> form which includes a button to delete the currently selected  
>> record and this works fine insofar as it deletes the record from  
>> the database but the fields and table all still show the record I  
>> just deleted.  I can "manually" refresh using a button tied to the  
>> refresh SQL action but I would like to force the refresh upon  
>> deletion of the record.  I can't find a transcript command which  
>> will force the tied fields to show the correct data without the  
>> additional user action of clicking another button.
>>
>