Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
Home
Discussion Groups
Database Servers
DB2InformixIngresMS SQLOraclePervasive.SQLPostgreSQLProgressSybase
Desktop Databases
FileMakerFoxProMS AccessParadox
General
General DB TopicsDatabase Theory
Related Topics
Java Development.NET DevelopmentVB DevelopmentMore Topics ...

Database Forum / FoxPro / SQL Queries / May 2005

Tip: Looking for answers? Try searching our database.

ThreadLast Post  Replies
select ... join27 May 2005 18:33 GMT3
I have a SELECT FROM Table_A, Table_B, Table_C ...
WHERE Table_A.Link1 = Table_B.Link1 AND Table_B.Link2 = Table_C.Link2 ...
How can I do this with INNER JOINs?
Thanks
Poor SQL query performance with FoxPro OLE DB27 May 2005 11:18 GMT1
My VB.NET application connects to FoxPro dbf (free table with cdx file) via
OLE DB 9.0 driver. I have about 100 000 records in the table. Simple query
“SELECT * FROM mytable WHERE id=’value’” runs about 7 seconds. The same
query written in native FoxPro syntax runs less than ...
calculated fields in remote view26 May 2005 23:31 GMT3
I am trying to create a remote view with calculated fields that use
functions such as PADR,IIF and
VAL.  I get "Connectivity error: Incorrect syntax"  every time I try to save
the view.
how could i fire trigger using vfp923 May 2005 16:31 GMT1
i had to fire the trigger before insert and delete in table login
which contains loginid,loginname,password.....for example
before insert or delete on the table login i want to fire trigger...
before insert or delete on login
Update statement does nothing21 May 2005 19:21 GMT2
I'm connecting to a VFP6 DB via the OLEDB driver.  I issue the following
Update statement:
update EMBTRAKQ set EMQPDT = {^2005/5/21 11:53} where EMQTAB = 'INVMASTER'
and EMQPID = 23
Foxpro 9 query performance problem18 May 2005 23:33 GMT1
I have a well established Fox 6 application that I am migrating to Fox 9.  I
have a probelm with performance.  All that I have change so far is set
enginebehaviour to 70 and tablevalidet to 0.  Everything else remains the
same as the Fox 6 compiled code.  If I run my query in Fox ...
enabling the config.fpw file???18 May 2005 00:28 GMT2
Just swapped from VFP 7 to 9 and I want to use a config.fpw file on startup
with the line "ENGINEBEHAVIOR=70" so that I don't have to re-write all of
the group by clasues on my hundreds of programs. I've created the file,
saved it in the c:\program files\visual foxpro 9 folder. Now, ...
removing duplicates16 May 2005 23:06 GMT4
hi friends
am wondering what is easiest way to delete duplicate records.
i have 3 fields (type,number,provider) which have duplicates and i want to
keep one of them delete the rest.
remote data tutorial12 May 2005 00:51 GMT2
Does anybody know of a good Promatrix tutorial on how to work with remote
data ?  The information in the Online help is kind of scattered.  I'd prefer
all the instructions compiled together in simple steps that I coudl follow.
Thank you
select giving both tables instead of 109 May 2005 13:21 GMT2
I have a vfp6 program where I want to create a file, acmast, with just the
fields from 1 file, npain, but get all the fields from the second file,
lelcin. I want to select only the npain records that are found in lecin as
shown below:
Visual FoxPro 6 SQL documentation03 May 2005 10:50 GMT5
Where can I find documentation of the SQL variant used by VFP6?  I find
plenty of stuff for versions 8 & 9 on the MSDN site, but I'm interfacing to
AMAS and told it's VFP6.
Thanks.
working with "not so"empty dates 02 May 2005 17:01 GMT6
I created an updatable remote view based on a SQL table, BLANKed out some
date fields, did the TABLEUPDATE and then REQUERY.  The fields show now
01/01/1900.
This confuses my application because I normally check for empty(date)  or
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread



©2008 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.