Error when deploying the InfoPath Form

I created an InfoPath Form with lot of validation rules.
52 check boxes with 10 rules each, don't give any issue when testing using InfoPath application.
But when I try to deploy, it gives an error:

"An XPath requires complicated processing which in not supported on InfoPath
Forms Services."

 InfoPath services on the MOSS install cannot handle the higher
calculation functions (XPath).

Is there a way to solve this issue.... :)

WSS User Accounts

User accounts for WSS users are maintained inside Active Directory, else you simply need to build or acquire an ASP.NET authentication provider that’s been designed to store and manage user accounts in an alternative identity repository such as a SQL Server database.

This architectural enhancement has led WSS 3.0 to gain much wider adoption as a platform for building Internet-facing sites.

For example, ASP.NET 2.0 ships with the forms authentication provider that allows you to maintain user accounts inside a SQL Server database. This authentication provider can be configured for use in a WSS 3.0 site. With little effort on your part, you can put a WSS site on the Internet that allows unknown users to register themselves as members. ASP.NET 2.0 provides you with convenient support for creating and maintaining user accounts, and even allows users to change and reset their passwords. When you use forms authentication, you can use the same programming techniques to manage user accounts in a WSS solution as you would in an ASP.NET 2.0 solution.

Difference between 32bit and 64bit :)

I guess you mean 32bit and 64 bit. Basically this number determines the amount of memory held in the registers of the processor. The 64bit windows can only be run by a 64 bit processor, but the 32 bit version can be run by both. Most processors today are 64bit capable so I guess this won't be a problem.
One drawback about the 64bit operating system is that any very old programs and drivers may have trouble working with the operating system. Microsoft has tried to get as many drivers as possible working in 64 bit, but they haven't been able to fix everything. If you're building from new parts though there shouldn't be much trouble. If you have a 5 year old printer/scanner or something though, it might not work.

Also, if you're planning on getting over 3gb of RAM you'd want to lean towards the 64bit version of the OS. The 32bit memory system can only hold a maximum of ~3.5 gb of RAM since that's the largest block of memory it can recognize. So if you put 4 gb of ram in a 32bit computer, it'll only see the first 3.5 gigs or so. The 64 bit OS increases the maximum RAM the operating system can handle to a huge amount that you won't have to worry about getting near for a long time.

[x32 is not the correct term in this case it is x86 which is the 32bit OS and x64 is the 64bit OS]

My SharePoint Site gives an error and doesn't load...

Parser Error
Description: An error occurred during the parsing of a resource required to service this request. Please review the following specific parse error details and modify your source file appropriately.

Parser Error Message: This page has encountered a critical error. Contact your system administrator if this problem persists.

Source Error: ....
________________________________________________________________________________
Some Solutions.. May solve the problem

1. Maybethe *.resx files have some strings missing,please check the server event viewer and 12\log files.  Also try an iis restart.
2. Web.config file got corrupted with "?" characters at random places in the file.(the question mark character   just got added on 12 different lines in the config file.)
       Fix:Removing those question markssolved the problem.
       So check if your web.config file is corrupted.
3. Assembly registered in the SafeControl-section referenced a non-existing assembly, and therefore the SafeMode did not start successfully.
   For detailed information about the error, you should have a look into the Application Event Log, where a detailed error message should be shown.

How to Uninstall and Install feature in SharePoint

(1). Uninstallfeature

stsadm -o uninstallfeature
   -filename <file name>
   -name <feature folder>
   -id <feature ID>
   [-force]

(2). Installfeature

stsadm -o activatefeature
   {-filename <relative path to Feature.xml> | -name <feature folder> | -id <feature ID>}
   [-url] <URL name>
   [-force]

How to install/uninstall a .wsp-File with stsadm

(1) INSTALL:

stsadm -o addsolution -filename path\mySolution.wsp
stsadm -o execadmsvcjobs
stsadm -o deploysolution -name mySolution.wsp -immediate -allowGacDeployment -force -allcontenturls



(2) UNINSTALL

stsadm -o retractsolution -name mySolution.wsp -immediate -allcontenturls
stsadm -o execadmsvcjobs
stsadm -o deletesolution -name mySolution.wsp -override
stsadm -o execadmsvcjobs

SharePoint, Ows_ in Property Mappings Tip

I want to thank Rich Rockwell at Thomson for his insights into this part of SharePoint Server 2007. In this post, I'm merely the messenger, he's really the author.
Let's say that we want to use a couple custom metadata columns in Advanced Search and we want to display the values in search results.  We are also using lists as look-up lists for the values for the metadata.
Now, we know that have to set up the Metadata Property Mappings to do that, but when we search for the crawled property to map to, we receive two values comtaining "product":  "Product(Text)" and "ows_Product(Text)". Which one should we use?
The first attempt was to use the one called Product(Text).  The result was that instead of seeing the "Title" values from the lookup table, we saw the ID number of the row (e.g, we got "2" instead of "AutEx AIOI"), and an advanced search for Product = AutEx AIOI returned no results, while an advanced search for Product = 2 returned items with a product of "AutEx AIOI."  So we changed the mapping to "ows_Product(Text)" and that gave us the "Title"/text value ("AutEx AIOI") and works in both the display for the search results page and for the advanced search.
Bill English
Mindsharp