ADO Timeout Expired
-
I have been delving heavily into VB.NET myself as a way to get away from Access, b/c of its 'issues' - like the ones you mention.
I just hope they get their reporting up to a better level, or upgrade access, to address some of these needs! I know they have to be pretty common issues given the typical business uses of data.
-
Hmm, maybe create a new Connection Object only when you go to retrive Data for your Recordsets. If Connection Pooling is on, this shouldn't be a huge resource hog.
As far as Reports go, maybe you could still Report from Access, but have the Users work in a seperate App =P. Or check out Crystal Reports or Active Reports or IntelliVIEW. Not sure if there are any more good ones out there.
-
quote:
I have been delving heavily into VB.NET myself as a way to get away from Access, b/c of its 'issues' - like the ones you mention.[insert applause here]
-
Heh, if you peeps need any insight in VB.NET, let me know. I have been developing with it now for over a year and know it pretty much inside and out. All I have to say is...read the Help files and check out http://www.codeproject.com! Good luck!
-
I'll take you up on that b/c I'm just starting, and have been doing T-sql for so long that all my VB skills (much less web programming) are completely rusty. Right now I can't even get my web server to talk to my database
-
Yes, that's a little more tricky but not too much. A great book is "ASP.NET Unleashed" by Stephen Walther (SAMS Press). Also, check out http://www.asp.net for more help and examples.
Viewing 6 posts - 16 through 21 (of 21 total)
You must be logged in to reply to this topic. Login to reply