Why the easy way in eVB 3.0 but too diffcult in VS.Net 2005 ?!

  • Thread starter Thread starter Chris
  • Start date Start date
C

Chris

Dear all,

I'm just wanna access a mdb file or any local database solution,
why so diffcult in VS.Net 2005 ?!
We need 3rd party or install many large application to finish this simpe
requirement ?!
Or just using .txt file is easy and simply way ?!

I can't understand why M$ trying to make diffcult to do this simple
requirement.
I almost lost my patience...

Chris
 
The reason is the same since allways: they want to push you to use their
new technologies, SQL Server in this case.

So you need to access data of current applications that is stored in MDB
format? that's your problem my friend.. not M$'s... they are giving you
a workaround (if this tricky-round-trip can be called so) and if you
don't like it... well, that is, AGAIN, your problem, not theirs.

This is the kind of things that keep many programmers far away of MS
development tools and technologies.

Sorry if I sounded ironic... is just that I HAD LOSTED my patient a long
ago with M$.

Victor Espina
 
The primary reason is becasue the CDB file is obsolete and no longfer
supported. Adding the capability to use it would encourage people to waste
time using a format that will no longer be used and waste developer
resources that could be spent making features that are useful. If you must
use CDB formats then there are existing workarounds and products.
 
Thanks for your reply my complain mail.
I'm just wanna know that the other developer how to solve this problem ?
It's just a easy function because the chance of who have office-Access is
more bigger
that who have SQL Server right ?

Chris
 
Back
Top