I'm a newbie and trying to get my head around all of this. If I do a fill on a BO like the Following:" Select * from stock where 1 = 2" and do a BO.Count it is obviously 0 even though the table has 100 records. That is OK but why when I do BO.Save() does all of the records remain? I think it has to do with no changes in BO but if I really want to remove all of the previous records in the table what is the quickest way? No relationships to worry about just a table that hold previous data and now needs to get all new data???? TIA.

Hi Terry,

I believe BO.Clear will do the trick.

Edhy Rijo

Terry -



I am a relative newbie as well, so take this with a grain of salt. The BO's functionality would be limited to the data it has in it's datastore. As there were no records retrieved as a result of your Fill() the "other" rows (the 100 in the table on the backend) would not be affected by anything you do with the BO's data.



HTH



________________

_____/ Regards,

____/ al




________________
_____/ Regards,
____/ al

Hi Edhy -



Good Morning! I've learned a lot from your postings, so I thought I'd say Thanks while I am here.



Wouldn't the .Clear( ) only operate on the rows the BO retrieved?



________________

_____/ Regards,

____/ al




________________
_____/ Regards,
____/ al

Hi Alex,

Thanks for the kind comments, I also learned a lot from others here and continue to do so everyday.

Yes, basically based on the comment in the SF source code, the BO.Clear method will do reset the data table with no records.

Edhy Rijo

These statements did not get rid of the 100 original records in the table.

I think there must be a way to get rid of the original 100 records with out an iteration thru the records but I have not found it yet. Thanks.

While I am here lets say Table A has the following Records(pk=primary key):

pk=1 stock=5

pk=2 stock=8

pk=3 stock=100

pk=4 stock=200

Suppose we use 8 and 100 and I want to write the remaining stock back to the table so the table contains:

pk=5 stock=5

pk=6 stock=200

The pk's are automagically generated. I know I used 8 and 100, how do I write the remaining stock back? TIA.

Hi Terry,

There must be something in the way you are checking the BO count.  Do the following test:

• Fill your BO with some records
• Test your BO.Count it should have the amount of records you filled with.
• Them do a BO.Clear, it should reset the BO.Count = 0

If I understand you correctly, you could have several records in your BO and out of those you just want to save a couple, if this is right, you can do this several ways:

• Have a flag field which will allow you to filter out the records you want to save, then use the BO.Filter = "MyFlagField = True" or something along those lines.
• Or you can iterate through all the BO records, copy the ones you want to save into another BO, then save the other BO.

If that was not what you meant, please let us know.

Edhy Rijo

Terry,



I'm not sure if this will help, but the BO is disconnected from the data. Thus, when you fill it, you lookup data in the db and load it into the BO. Once that is done, the BO isn't talking to the db any longer (until the BO needs to talk to it again, for another fill, to save or delete data). Thus, the Clear() method of the BO simply clears any data that was loaded into it, which has NO effect on the actual data (it's disconnected from it). This is great if you need to "smoke" (a bit of Texan vocabulary I picked up from Trent) the data in the BO in order to load another set of data into it.



However, if what you want is to actually delete data from the db, you need to go about it a bit differently. There are a couple of possibilities, depending on what you want to do.



First, if you already have the data loaded into the BO and you want to delete some or all of that data, you would add a method to the BO to loop through the rows of the BO and call Delete() on each row you want to delete. You would use a For loop and use the .Count property of the BO. Probably the most efficient way is to mark the rows for deletion and then do a Save() to actually delete them.



The second way is if you just need to delete a set of rows based on some criterion, like smokin all the records older than a certain date. In this case you would write a method in the BO that would accept the necessary parameters and either build some SQL or call a sproc to just execute a DELETE statement in the database.



I hope that clears up what some of your options might be in order to delete data in the db vs. clearing loaded data from a BO.

The first messagebox indiates 5 records which is what is there, the second indicates 0 which is what I would suspect and the third is 4 which is what I want.

Alright Alex, Edhy and Greg what am I missing here? Why when the above code in the simple Click of a Button is executed don't I get 4 records in the table instead of an error saying can not have duplicate Primary Keys. I am doing my own primary key right now. Even if I change the primary key to one that is not found in the table I then get 9 records instead of the 4 I want.

Do I need a SStockBO1.DeleteCurrentRow() instead of just a clear and save? Well I inserted this code

and of course it asked me about deleting each record(which I can not have in real life because there would be too many records) but I still get the same result? TIA

Terry,



Not sure I'm following your logic, so it is hard to offer detailed help. However, maybe I can offer some bits of help that will keep you moving.



First, this paradigm really isn't going to do anything:







Nothing will ever get saved. And if there were changes in the SwStockBO1, they'd be lost. Clear() removes all the rows in the underlying DataTable. Those rows drive if there is anything to save or not. A DataRow has a row state that indicates if it is dirty and how it is dirty (new, edited, deleted). When a Save() happens, it walks the rows and either adds, updates or deletes the rows. No rows to walk, nothing to do.



Because of this, the first part of your code never does anything in the database, thus the second part (were you add the new rows) fails, because those first four records are never deleted.



So, for the first part if you did something like:







You'd walk the first four rows of the BO, cache the "stock" value in your narray, mark those four rows for deletion, then actually delete those rows from the database when Save is called (and they'd be removed from the BO then as well).



If you just want to loop through the entire BO and delete every thing, you could also do:







Here I'm just using the count of the BO to drive the size of the array and the loop.



I just typed this in, so there might be some errors, but hopefully it helps you understand what is going on and gets you moving! Good luck!