Search results for query: *

You would still be able to use MSDE..

why don't you surround your code in a try { } catch { } statement? try { // whatever code throws an error } catch(Exception) { }

You could create new views for a list if you click om "Modify settings and columns" on the left side when viewing the list. When creating a view, you can pick which columns you'd like displayed. Also, the list of all views that you have defined should appear on the left side, and you could...

You could post here :) Also, a good resource would be the SharePoint admin guide: For Windows SharePoint Services: http://www.microsoft.com/downloads/details.aspx?familyid=A637EFF6-8224-4B19-A6A4-3E33FA13D230&displaylang=en For SharePoint Portal Server (if you have that)...

Also to add, Windows SharePoint Services (I think this is the one that's shown in the 30 day trial) is free. The only prerequisite you need is Windows Server 2003, after which you could download WSS from the Microsoft site...

calling HttpContext.Current.Request.UserHostAddress would give you the IP address. http://msdn2.microsoft.com/en-US/library/system.web.httprequest.userhostaddress(VS.80).aspx

This isn't so much a SharePoint issue/IIS issue, as a general "running a website on your own server" issue. For your friend to be able to access your server, somehow there has to be a connection between his computer and yours. If you are using the machine name (i.e. hapinder), that'll only work...

It sounds like you are on the right track by creating groups, and restricting access based on those groups. Unfortunately you can't have per-item permissions in WSS without a custom solution. However, you could grant/remove access to the groups to another sub-site, or a document library/list in...

When a list is created, there's a setting "Show on quick launch bar". You could later modify this settings by going to the list settings page (i.e. "Modify settings and columns.") To hide the Quick Launch bar completely, the following article describes one way to do it...

Hi ET, Since SPS is built on top of WSS, the schema.xml and such all are actually WSS features. On your own box, if you have WSS installed, check out the folder C:\Program Files\Common Files\Microsoft Shared\web server extensions\60\TEMPLATE\1033\STS\LISTS. You'll see a folder for each type of...

You could use the following C# code snippet... of course you'd have to compile it into an .exe to use it in a batch file. You can probably adapt this to a script solution too. string url = "http://yourserver"; SPSite site = new SPSite(url); SPWeb web = site.OpenWeb(); Guid g =...

If you install WSS SP2, the stsadm.exe tool will include a -o migrateuser command. The command will query AD for "SID history" that pseale mentions and migrate the user. You could use it as follows: stsadm -o migrateuser -oldlogin DOMAIN\user -newlogin DOMAIN2\user2 To automate the operation...

It sounds like you made an stsadm.exe site collection backup, rather than a SQL database backup. The article in KB827701 refers to the latter. stsadm.exe won't let you restore a backup that is *newer* than the current SharePoint version you have installed. For example, if you had SP2 installed...