View Complete Post
Hi, I'm trying to learn in the VS 2010 Express. Using the default template for ASP.Net Website. It starts the web application with an accounts folder. I'm trying to extend the "registration" or "AddUser" utilities. What I'd like to do is modify the registration by adding additional elements (i.e., address, city, ST, zip, etc.). I know I can open the database and modify the Users table and also modify the stored procedure for CreateUser.
My question is: I don't see any reference in the page code (here's a reprint of the register.aspx.vb) that calls the procedure, or even passes in the variables from the textbox entries from the page. I must be missing something. Can someone clue me how to drill into this template to find the elements like how it communicates with the database. There are a few JQuery files. I am not yet very familiar with JQuery. Is that where I need to look? Thanks for any advice...
Public Class Register
Protected Sub Page_Load(ByVal sender As Object, ByVal e As System.EventArgs) Handles Me.Load
RegisterUser.ContinueDestinationPageUrl = Request.QueryString("ReturnUrl")
Protected Sub RegisterUser_CreatedUser(ByVal sender As Object, ByVal e As EventArgs) Handles RegisterUser.CreatedUser
We have 100s of Infopath 2003 forms published on our Sharepoint site (MOSS 2007). These forms are updated constantly. The problem we have is that anytime we change the form's design (ex. change wording on the form), the user will get the
"Form Template Conflict" message when they click on the form. This is very confusing to them, and although we've asked them to click on "Replace form", they still get confused.
This message is very confusing to anyone, not just a user. We would like to suppress this message so that every single time we update a form, they don't have to see this. I'm not sure why it even saves a copy locally on their machines, anyway. The
fact is that in 100% of all cases, they will need to replace the form on their computer. Renaming the forms every time we edit them is not an option - there are too many and links would all be broken.
Can anyone tell us how to "hide" or "suppress" this error for our users? Or design a form on the back-end that won't show this? Could possibly changing security settings prevent this? Any suggestions would be appreciated on how to prevent
this message from popping every time we update a form.
I have changed the theme to Obsedian and I would also like to change the picture of the title bar of this theme and also the font/style of the title, top link bar, menus..etc. Is there a way to do this?
Please note: I am using WSS 3.0 and I am not the Administrator of the sharepoint. I am only the site admin of some sites on this sharepoint. I can do some basic customization using SPD.
Basically, what I am trying to do is that I want to set up a sharepoint site, however I want to make it NOT look like a sharepoint site.Well I know this is possible, but for my case it might be just partially possible due to the limitation that I am not
the Site collection admin and hence I do not have direct access to the server itself.
What I want is to hide most of the sharepoint links/menus/bars, etc and use my own buttons/hyperlinks etc .. for user to navigate on the sites.
Thanks in advance for your help/advices.
For Sharepoint 2010, Infopath 2010
When I trying to login Infopath by link Customize Form that available in the List tool bar I found the following error:
Infopath cannot generate a form template for the sharepoint list
The SOAP response indicates that an error occurred on the server
Can anybody help me figure out what is causing this error?
My form template has C# codes. I went through the process to publish it and link the generated content template type to my form lib pre-created.
So my question is Do I have to go over this process (publish, upload, activate it, link...) after I made any changes to the form or the codes?
If so, would be too much work!?
I have an interesting issue while deploying a VSTO enabled form today. For
some odd reason while performing stsadm -o verifyformtemplate -filename
foobar.xsn, it returned a "FatalError : The form cannot be converted because
it was designed for a later version of InfoPath Forms Services.".
Has anyone else tried deploying a InfoPath 2010 form with managed code in a
MOSS environment?? I'd hate to go back to InfoPath 2007, I love the new
I'm trying to create a new SP Feature that consists of the following components -- an InfoPath form, a document library (list) where these forms will be used, and a custom Task list (that will be used in a workflow that is triggered when the form is submitted).
Each of these components was created in a DEV env and is working. I then created my feature in Visual Studio 2008 and successfully created the WSP file. I then (successfully) installed the WSP (I got no errors on install and all seemed well --
the "solution" shows up under Central Admin and shows as being deployed.
When I go to site settings, the feature shows up, but deactivated. WHen I attempt to activate it, however, I get this error in the SP Logs:
09/24/2010 09:38:19.12 OWSTIMER.EXE (0x07C4) 0x07F0 Forms Server
Forms Services Deployment
82mz Exception FeatureInstalled failed with unhandled exception Microsoft.Office.InfoPath.Server.Util.InfoPathLocalizedException: This feature installing a form template does not match the expected format: CAPital EXpenditure Request. Refer to