>>>>In a number of places, I'm getting problems on the command line ??chr(7). For example, the program stops.
>>>>
>>>>Even though there are simple work arounds, I was wondering if anyone could tell me exactly how this works, so I that I can understand the problems.
>>>>
>>>>Thanks Mace
>>>Macer,
>>>Check your "set bell". ie:It might be possible you chose a wav file and your sound card have a DMA conflict.
>>>Cetin
>>
>>I've just taken a search through the messages, and there seem to be lots of little errors that occur in code that is using ??CHR(7) from tableupdates to moving bmps, and I have developed a theory :-), but I don't know how to replicate it :-(.
>>
>>From the docs '??' evaluates the command and writes it to the main VFP window. What would happen if for some reason VFP couldn't write to the main VFP window. I have a feeling this is why the code is hanging on this line.
>>
>>Can anyone proove or disproove my theory or am I just barking?
>>
>>Mace
>Documents are wrong then I would say. ?? outputs to active window, current cursor position ("set alternate", "set print" etc also effect and might be a blockage for outputting).
>? does line feed before output, ?? doesn't.
>chr(7) is simply a nonprintable character "dinging" bell. If you suspect chr(7) itself is responsible replace it with something else ie: "x". If it works w/o error, check your sound system from control panel.
>Cetin


Cetin!!!

You're a star. I replaced the chr(7) with a chr(120) and got the same bug - fox hung. I took a quick peek at the active form and there in my combobox - drop down list style - was a little grey 'x'

So, it is hanging because it can't write to whereever it writes to - in this case a combo! Ulan!!

I'm assuming if use the API call I'll be OK. I'll try it tomorrow - but right now my stomach is calling for my dinner.

Thanks for your help guys

Mace