Re: APPEND BLANK with immediate field values set right after

2019-10-03 Thread Ted Roche
On Thu, Oct 3, 2019 at 10:45 AM wrote: > Sorry but SQL INSERT always does position on the new record. This is > documented even in the helpfile: > OK, w00dy, thanks for the correction. My VFP knowledge is legacy these days ¯\_(ツ)_/¯. Ask me about MariaDB 10 or PHP 7 on Linux :) I think the key

AW: APPEND BLANK with immediate field values set right after

2019-10-03 Thread juergen
Sorry but SQL INSERT always does position on the new record. This is documented even in the helpfile: - If the table you specify is open, SQL INSERT appends the new record to the table. If the table is open in a work area

Re: APPEND BLANK with immediate field values set right after

2019-10-03 Thread Ted Roche
On Thu, Oct 3, 2019 at 9:50 AM Peter Cushing wrote: > > Just looked at the help file and it says > "After executing the *INSERT* command, Visual FoxPro positions the > record pointer on the new record." > I did say "I think" as my Fox days are pretty much behind me. > I'm sure I have some code

Re: APPEND BLANK with immediate field values set right after

2019-10-03 Thread Peter Cushing
On 03/10/2019 14:15, Ted Roche wrote: > > Well a minor difference, I think: APPEND BLANK / REPLACE changes the > RECNO() to the record being added to, where INSERT INTO may not. If other > code tries a REPLACE without locating the proper record, you could end up > changing the wron

Re: APPEND BLANK with immediate field values set right after

2019-10-03 Thread Ted Roche
On Thu, Oct 3, 2019 at 4:51 AM wrote: > Hi Mike, > I have seen this coding style sometimes. > Yes, you can change the APPEND BLANK / REPLACE combos with an INSERT INTO > without any negative siedeeffects. > Well a minor difference, I think: APPEND BLANK / REPLACE changes the

AW: APPEND BLANK with immediate field values set right after

2019-10-03 Thread juergen
Hi Mike, I have seen this coding style sometimes. Yes, you can change the APPEND BLANK / REPLACE combos with an INSERT INTO without any negative siedeeffects. The part with that GO BOTTOM / SEEK() was normally done for repositioning other tables, which are linked with a SET RELATION. You could

APPEND BLANK with immediate field values set right after

2019-10-02 Thread MB Software Solutions, LLC
In trying to find the "demons" in this legacy VFP app (shared/used by both desktop and internet/website users), I find there's a lot of APPEND BLANKS everywhere followed by an immediate REPLACE (and sometimes more than 1).  Here's a sample of my findings:  SELECT notes  A

Re: Append blank

2011-09-07 Thread Vincent Teachout
Fred Taylor wrote: > SELECT * FROM cursor1 ; > UNION ALL > SELECT * FROM cursor2; > etc > INTO CURSOR curall READWRITE > > Fred Fred's way is probably the best for this particular problem. However, to answer your question, since it may be of use in the future, you can't append into a table dir

RE: Append blank

2011-09-07 Thread Kent Belan
Email List Subject: Re: Append blank SELECT * FROM cursor1 ; UNION ALL SELECT * FROM cursor2; etc INTO CURSOR curall READWRITE Fred On Wed, Sep 7, 2011 at 3:27 PM, Kent Belan wrote: > Hello, > > I am working on a business object layer routine that I need to combine > the result

Re: Append blank

2011-09-07 Thread Fred Taylor
SELECT * FROM cursor1 ; UNION ALL SELECT * FROM cursor2; etc INTO CURSOR curall READWRITE Fred On Wed, Sep 7, 2011 at 3:27 PM, Kent Belan wrote: > Hello, > > I am working on a business object layer routine that I need to combine the > results of several tables into one cursor. All the tables h

Append blank

2011-09-07 Thread Kent Belan
Hello, I am working on a business object layer routine that I need to combine the results of several tables into one cursor. All the tables have the same layout. I am creating the cursor for the first table like: Select * from table1 where conditions into cursor1 Then I loop thru the tables and