DBA question...

[Jeff Lane]

Actually you can have a DBA hold a DBA. I've seen it done several times.

In fact about a dozen years ago I had an investigation that was very hard due to this.

That's an interesting story, but it points out something that should be said about registering a DBA.

The whole point of having a DBA registry is to that the public can actually FIND the responsible party if they need to for some reason (like suing for damages). For that reason, if the clerk catches it (which would have been hard in the case Brian cited, and I suspect it's because this "Smith/Gates" guy was trying to be too clever by half to get away with chicanery or worse), a DBA should only be issued to either a "natural person" (meaning a human being, not necessarily an organic gardener or someone who shuns polyester garments) or a duly constituted business entity.

[Steelsun]

Yeah, it's one of those things you "can do" but really shouldn't. The guy in this case was trying to be deceitful. He ended up paying in the end (lots of moolah)

[jordankreationz]

Hahahaha. I love your analogy. You just made a really boring night at work a little funnier. Sorry that this was off topic. Just had to comment.

Originally Posted by Jeff Lane

It's a little like this: My Lovely Bride (hereinafter, "MLB") sometimes calls me "Honey" when there are honey-dos to be honey-done, and sometimes "Handsome" when she's lying but feeling amorous nonetheless (I almost never hear that one), or "Sweet Daddy Warbucks" when she wants access to my wallet (even though "Handsome" would work better for that purpose). Three different DBAs for one guy, depending on what "service" I'm selling her. (By the way, there are a whole slew of other names she calls me when she's unhappy, and I hear those ALL the time, but I guess that's where the analogy breaks down.)