Converting Over

  • First time sql server central poster, although I have been a member for a little while and have been using this site to answer questions I have from time to time.

    Here's my problem.

    I have an MS access front end reporting tool with a sql back end that I originally developed for small time use.  Turns out the project was a big hit and it needs to be rolled out to a large group of people.

    So, I am going to develop all the forms and such I have already written in access in visual basic.net to make them more secure, but I am rather unfamiliar with visual basic.  All of the queries I have written already in the Access front end use multiple variables that the user enters in on a form, text boxes for the most part.

    I can rewrite the queries that i have in MS Access into veiws in SQL but I can't figure out how to make the variables pass through a basic form I created in .net.

    How does this work?  Am I going about this the wrong way?

  • Well if you created views then yes. You need to create stored procedures that have parameters to filter the result set.

    One other thing you could do is an Access data project (sql server back end, access front end). Same as you did, but without any linked tables (not sure how you did this). I think it can be as secure as the vb net prog you intend to do. You just need to give access only to the minimum amount of objects on the server and you'll be fine.

  • I could write the stored procedure, but my problem is I can't figure out how to tie the query to the form. 

    When I write it in access for example you do the

    !Forms!Frm_reports!txt_something

    in order to point the query to the form.  I can't figure out how to tie it like that to a VB form...

    I guess I could keep it in access, my understanding is that its not as secure, and that it won't be able to handle a large amount of users, which is why I think going to VB is the solution.

  • You can't do it that way without a reporting tool like access or crystal report. You'll have to manually open the recordset with a command object and then present it yourself.

  • vb.net wont link to it like access will?

  • I've never done reporting in .net. I don't think it's gonna be easy to convert that project to .net if you've never worked with it.

    Also access has been created to help non programmers do some forms and reports using wizards. It's really not the same thinking line that is used for .net. You really need to know what you're doing to code in that language (compared to access).

  • okay well thanks a lot for the input!

  • If you have VB6 available, consider using that instead of .NET.  You can include an ActiveX control on your VB6 form that connects to your backend and then the references are very similar to MS Access.

    (This is why there is currently a backlash against MS stopping support for VB6, .NET just doesn't do some things as well!)

  • All data access in .NET is done through ADO.NET...that's how you get the variables through from the form to the database, then the database records back out to the web page.  ADO.NET is a general purpose class library for accessing data sources of many different types.  The cool thing about ADO is, you can learn it once, then use it when dealing with SQL, Access, XML, DB2, etc.  Well worth the time. 

    Web front ends are what it's all about.  You've been given the opportunity to expand your knowledge on this, so you should DO IT!  Get a couple of books (go to the library or bookstore and leaf through a bunch...or Amazon).  Get one on ADO.NET and one on VB.NET, and then start coding.  You'll have a simple web page up in no time; and it will all start coming together.  Then, when you're done; you ask for more money, or go get a better job.

    Good luck!

     

    Signature is NULL

  • Okay, I'll figure it out with ado.net then.

    Thanks!

Viewing 10 posts - 1 through 9 (of 9 total)

You must be logged in to reply to this topic. Login to reply