Search results

So the consensus is that dates may be required sometimes? Since dates are only marginally more difficult to implement, and since once implemented it just works however it works, let us use dates?

Which aptly points out that it is the client who decides things. Tell me what you need and I will figure out how to make that happen.

Implementation cost is more than storage. It is also reporting, decisions, meetings, new hires to handle more reporting, decisions and meetings etc. As I mentioned in a previous post, capturing every bit of data that exists has costs. I am not arguing with you, I am simply pointing things...

Ok, understood. Except that deleting orders? Are you immediately archiving your orders or something? Why is the order being deleted? In any event, if you need to know when, then you need to know when. Business rules are not my domain, implementing business rules is my domain.

One thing that I tried to stress with my clients is that collecting every piece of data in the world doesn't work. Anything you decide to collect needs to be reliably and religiously entered or... it ends up being a detriment rather than a benefit. Ever run into data missing in reports? Yea...

The whole "who done it" is also a whole nuther discussion. Are we implementing an audit trail as well? Certainly not in this class specifically I would think. I would really love to implement an audit trail but it gets real deep real quick. My feeling is that if something is happening that...

Let's discuss for a minute date vs boolean. Once we get into "when it was done, in my mind that information has to be worth the effort to deal with it. For example for the active flag, knowing when a client was set inactive might be useful. Why / how would it be useful? Knowing when a record...

That is fine. Some fo Some folks want to record who did the delete. Whatever works for you and your client. For me and my clients a simple "it has been done" works. I can see recording the date that a client was marked inactive. That makes sense and is usable data. When a record was...

Any thing that is not active, is trash. So why you need 2 where 1 can do the same. We have 1 long text field (why), an integer field (who), a datetime field (when) for deleted records. Not true as explained Supervisors don't want to see the deleted records all over the place. Every search form...

I never said anything not active is trash. A client can be inactive but we need to keep their stuff around. NOT trash!

Active and trash are independent. A record can be activeor inactive. Think a client. They haven't ordered anything in a year and the company poilcy is that if a client hasn't ordered by X they are inactive. But the client isn't trash. They are not going to be deleted. Probably ever. OTOH...

And you realize that this really hurts the worm. And you realize that this really hurts the fish. And you realize this really hurts your finger And you realize that fishing isn't what it is cracked up to be. Not that I tell my daughter that. The excitement when she catches a "really big fish"...

Yea, behind me!

Well boy aren't you the ultimate encouragement! ;) I spent a year trying and failing before I got it. I am trying to make it easier for the uneducated to become educated. And @Gasman has been a huge help in that regard.

I use classes to generalize activities in the user interface. The objective is to standardize the interface across forms. For example every form can have an active / trash capability without having to do that in every form's code-behind-form class. One example from my past, I used a pair of...

@Gasman, you are hitting a wall. Go fishing. You will be struggling to get a worm on the hook when the Aha moment arrives. No not that aha moment, where the hook gouges your finger...

Sigh. I appreciate all you have done. I was getting ready to introduce clsActiveTrash! A pair of check boxes, bound to a pair of boolean fields, used to allow the dev to prevent deletions and yet allow the user to think they had deleted stuff. This is a great class to earn pizza from the...

@Gasman you are doing a great job with this. I think you are almost there. You are asking a class you create for some information about something. In this case you need the name of the control stored in the class header. Property Get / let / set is the "interface" for a class to do what you...

It could be the name of the button but a compiler is very specific. In the alphacommand class - the thing that stores the actual command button - Property get Name() as string Name = CmdButton.name '(or whatever the command button variable is called) end property This "exposes" the name...

No Gasman. Stupid means unable to learn. You are uneducated. We are trying to educate you. Just bear with us please. It takes that aha moment but it will happen.