You searched for the word(s): userid:673519

More Search Options

RSS Available

• Re: Publish Walkthrough

  It's been awhile since I did this but I'll give it a try. In order to get my website (which is internal so I can't show it to you) to work I: 1. Opened IIS and stopped the default company website that is packaged with the OS from running. 2. I created a new website called CANCIS 3. I clicked on the properties for the site, clicked the documents tab, enabled default documents and typed in the name of mine: default.aspx 4. The host header section came up when I created the site. I just

  Posted to Configuration and Deployment (Forum) by Drummos on 10/1/2007

• Re: SQLDateTime Overflow on Formview delete

  I was able to fix this. I have a data access layer with the data sets in it and a business logic layer. On the table in the DAL I changed the generated code to read: Delete From Table Where fldID = @fldID The generated code had all of my table fields in it. In the BLL I changed my method to: <System.ComponentModel.DataObjectMethodAttribute(System.ComponentModel.DataObjectMethodType.Delete, True )> _ Public Function DeleteClientApp( ByVal fldMainSSN As String ) As Boolean Dim rowsAffected As

  Posted to Data Presentation Controls (Forum) by Drummos on 4/13/2007

• Re: SQLDateTime Overflow on Formview delete

  You know I'm not sure that this error is generated by the datetime field itself. I think my formviews are kicking out errors on fields that aren't supposed to have null values. For example, I tested the delete function in a different formview and got an error on the primary key field that the value could not be null. Anyone run into this before?

  Posted to Data Presentation Controls (Forum) by Drummos on 4/13/2007

• Re: SQLDateTime Overflow on Formview delete

  Well hmmm, here is why I probably wrote in all the parameters. Following is the new code and after that is the error message I get. 1 <System.ComponentModel.DataObjectMethodAttribute(System.ComponentModel.DataObjectMethodType.Delete, True )> _ 2 Public Function DeleteClientApp( ByVal fldMainSSN As String ) As Boolean 3 4 Dim rowsAffected As Integer = Adapter.Delete(fldMainSSN) 5 6 'Return true if precisely one row was deleted, otherwise false 7 Return rowsAffected = 1 8 End Function Error 7

  Posted to Data Presentation Controls (Forum) by Drummos on 4/12/2007

• Re: SQLDateTime Overflow on Formview delete

  You know I was thinking about that as I made my post. Probably because I was following the 3 tier tutorial and it was my first time working with a class or a BLL that I didn't think about it. I'm going to get rid of the parameters accept the ID field and maybe that will solve my problem.

  Posted to Data Presentation Controls (Forum) by Drummos on 4/12/2007

• Re: SQLDateTime Overflow on Formview delete

  Thank you for responding. I read some of the articles and I guess I'm just not getting how to apply the information to the delete scenario. It would be easier if I was editing or inserting data to do a conversion but those functions are working just fine. Here is my delete code in the BLL if it helps: 1 <System.ComponentModel.DataObjectMethodAttribute(System.ComponentModel.DataObjectMethodType.Delete, True )> _ 2 Public Function DeleteClientApp( ByVal fldIntake As DateTime, ByVal fldMainSSN

  Posted to Data Presentation Controls (Forum) by Drummos on 4/12/2007

• SQLDateTime Overflow on Formview delete

  I can't get the delete button on the form view to work. I think it is because the date field becomes empty and so it throws the SQLDateTime Overflow error. Does anyone know how to fix this? I'm using a business logic layer. I did try to do something like this in my delete parameters statement: fldIntake as nullable(of datetime) This stops the overflow error but then the delete command link doesn't do anything at all.

  Posted to Data Presentation Controls (Forum) by Drummos on 4/11/2007

• Re: Publish Walkthrough

  LOL. Yea, kinda. BUT I finally reached success today with some help from a fellow on learnvisualstudio.net I had to stop the default website from running in IIS and then remove the host header from my website. After that I got success. Yea! Now I need to work on logings to the database :)

  Posted to Configuration and Deployment (Forum) by Drummos on 4/10/2007

• Re: Publish Walkthrough

  I unchecked the box. If I type in http://cancis/default.aspx then it looks like a 404 error. If I type in http://localhost/cancis/default.aspx then it comes back with server error in /cancis application. It's the typical yellow screen you get when a page does not load correctly in visual studio. It looks like all my playing around messed up my data access layer. The connection string on web.config isn't loading and I can't open one of my data sets. That might be my problem now.

  Posted to Configuration and Deployment (Forum) by Drummos on 4/8/2007

• Re: Publish Walkthrough

  I think I found part of the problem. The default web site runs asp v1 and will not run asp v.2. I created a new website called cancis, gave it a new apppool called cancisAppPool. I linked it to the directory c:/cancis I still cannot browse the page. This is driving me nuts. On the properties for the cancis site I included default.aspx as my start page and made sure that the asp version was asp v.2.0.50727 When I try to browse the site through IIS I get Internet Explorer cannot display the webpage

  Posted to Configuration and Deployment (Forum) by Drummos on 4/8/2007