Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
Why is append blank adding two records?
Message
From
03/11/1997 11:54:43
 
 
To
02/11/1997 01:23:18
Larry Long
ProgRes (Programming Resources)
Georgia, United States
General information
Forum:
Visual FoxPro
Category:
Other
Miscellaneous
Thread ID:
00057230
Message ID:
00057990
Views:
45
>>>>thanks Larry - I will try this. please excuse me if this is a dup messaage.
>>>>Without using buffering everything is working good, but when I APPEND BLANK,
>>>>the record pointer to going to the last record instead of adding a blank
>>>>record at the end. Do you know why? thanks
>>>>also, once you told me how to add. You said to use up all the deleted
>>>>records and then append blank. In a single user system, I do not see
>>>>why you should use buffering at all. If the users aborts, just delete the
>>>>record and use it the next time the user wants to add. What to you think?
>>>>You can always APPEND BLANK OR INSERT INTO for adding.
>>>>I did try using INSERT INTO like to said, but I got a messsage saying I needed
>>>>to be in exclusive mood.
>>>>please comment :)))
>>>Robert,
>>>
>>>First off if you write your app as a multiuser app from the start it will not require rewriting later when it needs to become multiuser.
>>>
>>>If you got a message about exclusive use then you were using the old xBase Insert commadn and not the SQL INSERT INTO command, check the help file for syntax. If the help file says "included for backwards compatibility" then it is not the one you want.
>>I guess it is that I have so many options, that I have not settled..
>>you no what I mean...
>It's been so long since I have used the "regular" insert, that I forgot about it. Was that your problem? As far as your other question about buffering, technically I agree with the above statement. It boils down to who is paying for the program? It takes significantly longer to produce a good multi-user app (at least up front time). If you (or the guy with the $) sees no future in expanding the program for multi-user, then most likely, the project is already dead. If the owner of the program sees even the remote possibilty of the program expanding, then the cost of making the first app multi user is much less than the prospect of a total re-write a year or two down the road. //:^)
I agree - I thought I would make all apps multiuser and just turn set
exclusive on or turn off a switch. But maybe not.. :))
Robert Keith
Independent Developer
San Antonio, Texas
E-mail address:
rebelrob1@yahoo.com
Previous
Reply
Map
View

Click here to load this message in the networking platform