General discussion

Locked

ADO Data Control Limitations

By afisher ·
What limitations does the ADO Data Control in VB 6 have that should cause me to avoid it in favor of coding data access procedures from scratch? Thanks!

This conversation is currently closed to new comments.

3 total posts (Page 1 of 1)  
| Thread display: Collapse - | Expand +

All Comments

Collapse -

ADO Data Control Limitations

by andrew In reply to ADO Data Control Limitati ...

To be honest, I've never used the ADODC, but here are my thoughts:

I think the major limitations whould be flexibility and architecture. If your application has just a few forms and requires a graphical record changer (next, last...) then the ADODC would be ok. If you have many forms, and need to access data based on queries and business rules (more real-world)then the ADODC would be clunky.

Relying on the ADODC would make switching front ends or back ends difficult. If you wanted to moveto a web interface or an n-tier design, you'd need to rewrite a lot of data access code.

I've always written the data access code myself. It's very flexible (I have Win32 and ASP/HTML front ends on the same data access code), fast and the libraries can be shared between projects, and it's not too laborious.

Collapse -

ADO Data Control Limitations

by afisher In reply to ADO Data Control Limitati ...

Poster rated this answer

Collapse -

ADO Data Control Limitations

by afisher In reply to ADO Data Control Limitati ...

This question was closed by the author

Back to Web Development Forum
3 total posts (Page 1 of 1)  

Related Discussions

Related Forums