This is REALLY starting to bug me.
I have been coding a multi-threaded DLL to provide an interface between a
ASP based application and our main VFP 9 application.
I am now starting to get these errors which you would think are permissions

I have a PopUp menu associated with a button on one of my forms - having a
Grid Control as well - , when the PopUp menu is active and User Presses
'ESCAPE' Key the grid goes off and form becomes unstable ???
I want only the popup menu to get disappear in this case. Any help tip ...

I have a form - which is part of a formset - open and we click the
Applications Exit button - Not the Forms Exit Button - the open form window
is not released even with the Release Window (WOutPut()) Command ?
What can be the reason that a window defined is not released even by ...

How do I release a COM object without releasing the variable referring to
the COM object?
I have an object that refers to a COM object created by a call to
CREATEOBJECT().  Most of the time, I need one and only one instance of this

does anyone know how to auto-hide the windows taskbar

Is there a way (an API, perl module, anything) to connect to an offline
Exchange database, and extract emails/mailboxes?
Thanks,
Martin

There is the statement
select *, 1 as ck from  cursor_name into array array_name
How can I make the array array_name public?
Or is it possible to make an array public?

After creating
a form object
I need to take value (not public)
to some variable.

Is it possible to change a cursor to have an opportunity to add columns,
change values ?
What should I do for this purpose ?
The normal cursor is for read-only .

we are using vfp8 SP1.
When the following line is run we are getting an error
ALTER TABLE tcustrate add new l(1)
The error reads error:1

    I have been looking at reworking parts of my app.
 1) If I have a form written in code, is there any way I can get the
return value from the form's .unload()?
 2) As it stands now, my forms are modal.  I am looking at changing

What would cause macros to act inconsistantly? They work on some
machines and not others? I can't say all macros within the application,
but one particular very small program within the entire app seems to
work on some machines and not others.

Over the last few months... Is it just me, or has the demand for FoxPro
development dropped even below its usual abysmal level?

I am having some problems with tables, which appear to be closing even
though there is no code that would close them.  No tables are open or closed
and the work area is not changed during the process.  Below are some
examples of the code and the errors.

This is an odd issue I just ran into that I that seems to occur in VFP7,8,9.
I have several fields in a detail band (also does the same thing if in
header, the fact that it's the detail band is not significant). The fields
are layed out like this, included the dashed lines above ...