Have you as an ADP user, been happier with results then with MDB's?

[markphsd]

I know this could yeild lots of results, but I'd just like to read some of them.

Mark P.

http://www.cafecartel.com

Providing Low Cost Powerful Point of Sale Solutions.

 

[ronspree]

The short answer is yes and no. Haha. The longer answer would be "it depends on your application". If your application will be on a single computer, im a lot happier with mdb.

For multiuser and multi-computer applications involving lots of data, mdb seems to suffer considerably in performance. This is where mdb would start to make you miserable and, the formidable adp begins to be an attractive alternative.

There are lots of other reasons. To generalize them, if the application is simple, use mdb. If not simple, use adp. The drawback is you have to be knowledgeable in both, and they are not so similar as you would like to believe. But then, their differences is what makes them both uniquely beautiful.

 

[markphsd]

I know the differences, i've worked with both. But now that adp has been out for a while, i was hoping to see how it's been working for developers.

Mark P.

http://www.cafecartel.com

Providing Low Cost Powerful Point of Sale Solutions.

 

[ronspree]

I see. Well, yes I've been happy with some of the adp applications I made. However, there are also some that is better off as an mdb. For example, I have this sales data entry program. Im so much happier with the adp version. On the other hand, I have this check writing application that turned out to be such a horrendous task to implement in adp. This time, the mdb version is more desirable.

So for the right application, you can be happier with adp.

Between the two, however, I have to admit that I have had more headaches with adp.