Search results for query: *

Thanks - but that's one of the first things I checked . Also, this only happend when the "TO FILE" clause is included. If directed to print or preview everythings fine. LCB Puritanism - the secret fear that someone, somewhere is having fun.

(simplified example of issue) TABLE 1 - Customers TABLE 2 - Contracts. I have a process that scans through table 1, then scans table 2 for Contracts associated with the customer in table 1. When this data is collected I then issue a "REPORT FORM TO FILE" that generates a report which...

Cool... Have written code to send mail many times... never had to read it. Now I know ! Learn something new every day. LCB Puritanism - the secret fear that someone, somewhere is having fun.

Gotta admit I don't know of any way to do this. I do know that on exchange server you can trigger scripts to run on event occurance.. I would try to create a server script that saves the body to a pre defined file name , and then have my FoxPro app look for the existance of that file...

Another Vote for VSS. I also have had problems when linking it directly with Foxpro though. Much better luck running them stand alone. LCB Puritanism - the secret fear that someone, somewhere is having fu.

I believe issuing "SET TALK OFF" whill do what you ask.

Views are associated with Databases. See the following from Hackers Guide. CREATE/DELETE SQL VIEW These commands add and remove both local and remote views from a database. CREATE SQL VIEW is rather long-winded, but it must be, because CREATE VIEW is an old (useless) Xbase command.

I generally design everything for 800 X 600 resolution. Don't seem to have many users set to 640 anymore. For more info see ... http://support.microsoft.com/support/kb/articles/Q128/2/02.asp

How are you defing the rowsource for the listbox ? What is the rowsource type ?

FoxFire is what I've always used. transports well with VFP apps and from talking to my end users is about as user friendly as Crystal.

I've got an app installed in over 700 installations which instantiates a Server based DCOM object that retrieves data from a SQL 7.0 database and sends it back to the client in ADO recordsets. This works fine until a few users attempt to instantiate the object over certain cable systems...