bang head here Posted January 24, 2003 Posted January 24, 2003 Is this error any different in NET as is was in classic ASP? I'm getting it now and tried the permission route that worked in the past, with no luck. Does anyone know if MS made this stupid error more of a blanket than it was in the past? Thanks. Quote
Moderators Robby Posted January 24, 2003 Moderators Posted January 24, 2003 Place a Try/Catch in your function and see what the Exception is. Quote Visit...Bassic Software
bang head here Posted January 27, 2003 Author Posted January 27, 2003 I decided to bail on the jet/Access thing for now and use SQL Server for the development. Jet seems really outdated in .NET now. thanks! Quote
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.