仅使用 Windows SharePoint Services 3.0 制作表单？
在大多数情况下，我的组织对 WSS 3.0 很满意（无需升级到 MOSS），但有一个例外，我们实际上只想以某种方式提供一种表单。 这是一个相当大的表格（基本上是 IT 服务的变更请求，在纸面上很容易就有 2 个完整的 8.5 x 11 页）。 我们考虑将自定义 ASP.NET 编码作为单独的独立页面或 Web 部件。 其他人做了什么？ MOSS 和 Infopath 并不是真正的选择，因为目前它对我们来说确实太贵了。 提前致谢！
For the most part my organization is happy with WSS 3.0 (no upgrading to MOSS) with one exception, there is really just one form we'd like to put up somehow. It's fairly big form (basically change requests for IT services, on paper it's easily 2 full 8.5 by 11 pages). We thought about Custom ASP.NET coding as a separate stand-alone page or maybe as a web part. What have other people out there done? MOSS and Infopath is not really an option as it really is too expensive for us at this time. Thanks in advance!
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（7）
您可以将其构建为独立的 HTML/ASP.Net 页面并将其包含为页面查看器 Web 部件，也可以为其创建自己的 Web 部件。 如果您还不了解 SharePoint 开发，后者会稍微复杂一些，尽管 STSDEV 等工具可以使用远离很多痛苦。
You could either build it as a standalone HTML/ASP.Net page and include it as a page viewer webpart, or roll your own WebPart for it. The latter is somewhat more complicated if you don't already know SharePoint development, although tools like STSDEV can take away a lot of the pain.
如果您必须自己开发，请直接在 asp.net 中进行。 没有理由在 sharepoint 中这样做。 学习曲线很陡峭。 对于一次性解决方案来说，开发基础设施过于繁重。
大多数时候，IT 服务的变更请求是工作流程的一部分。 我相信最好的工作流程工具是错误跟踪器。 他们使用基于状态的工作流程。 在大多数情况下，这更适合现实世界。 所以，如果你有这样的工具，你应该有。 检查要使用的选项用于变更请求管理。
If you have to develop it yourself, Do it in straight asp.net. There is no reason to do it in sharepoint. The learning curve is steep. The development infrastructure is to heavy for a one off solution.
Change request for IT services is part of a workflow most of the time. I believe that the best workflow tools are bug trackers. They use a state base workflow. Which fits better, in most scenario, the real world. So, If you have such a tool, and you should have. Check the option to use is for change requests management.
您可以使用 Infowise Smart List Pro 完成大部分工作。
它旨在成为满足 80% 常见表单需求的简单解决方案。 它通过出色的 SharePoint 列表增强功能来实现这一点，例如字段权限、选项卡式视图、查看权限、默认值、规则等。
令人高兴的是，Smart List Pro 不需要 MOSS 或 SharePoint Server。 它只能在 WSS 或 SharePoint Foundation 上运行。
它在 WSS 3.0 和 SharePoint 2010 上运行良好。
以下是链接：http://www .infowisesolutions.com/product.aspx?id=SmartListPro
You can accomplish most of this with Infowise Smart List Pro.
It designed to be an easy solution for 80% of the common form needs. it does it with great SharePoint List enhancements like - Field Permission, Tabbed View, View Permission, Default Values, Rules and more.
The grates thing is that Smart List Pro does not require MOSS Or SharePoint Server. it can run on WSS or SharePoint Foundations only.
It works fine on WSS 3.0 And SharePoint 2010.
Here is the link: http://www.infowisesolutions.com/product.aspx?id=SmartListPro
您可以将 SharePoint 设计器与 WSS v3 结合使用
You can use SharePoint designer with WSS v3
您可能需要考虑简化变更请求表单。 2 页的内容对于变更请求来说是相当多的信息。
我使用标准共享点列表来收集变更请求，并发现我很幸运让人们填写前 4-5 个字段。
数据视图 Web 部件可用于添加数据，而不是标准的新项目表单。
You might want to consider simplifying the change request form. 2 pages of stuff is rather a lot of info to fill in for a change request.
I use standard sharepoint lists for collecting change requests and find that I am lucky to get people to fill in the first 4-5 fields.
The dataview webpart can be used to add data instead of the standard new item form.
调查列表是表单的一个很好的简单替代方案，并且无需任何编码即可使用。 输入“问题”，即。 输入字段，然后附加插入邮件提醒。 缺点是您无法控制表单的布局，每个输入字段严格只有一行。 这使得它可能不适合大型表单。 但它是如此容易使用，所以无论如何你都应该看一下它。
如果您决定自行开发，请编写一个 Web 部件，并将其添加到 WSS 页面。 （最简单的部署：继承ASP.Net WebPart类，放入GAC中，在SharePoint webapp的wpcatalog文件夹中创建一个.webpart文件）。 对于写道 SharePoint 的学习曲线太陡的人，我认为如果您将 WSS 用于内部 Web 应用程序，您将来会发现对 SharePoint 自定义的更多需求。 学习如何做到这一点是一项很好的投资。
The Survey list is a good simple alternative to forms, and can be used without any coding. Enter the "questions" ie. input fields, then attach a mail alert for inserts. The drawback is that you have no control over the layout of the form, it is strictly one row per input field. This makes it perhaps not a good candidate for your large forms. But it is so easy to use that you should take a look at it anyway.
If you decide to develop yourself, write a web part, and add it to a WSS page. (Simplest deployment: Inherit from the ASP.Net WebPart class, put in GAC, create a .webpart file in the SharePoint webapp's wpcatalog folder). Re the person who wrote that the learning curve in SharePoint is too steep, I assume that if you're using WSS for your internal web applications you'll discover more needs for SharePoint customization in the future. Learning how to do that is a good investment.
我想说的最好方法是创建一个 Web 用户控件并将其添加到 Web 部件（容器 Web 部件） - 用户控件可以添加到 12 个配置单元中并从那里选取。 我已经尝试过了，鉴于页面有很多内容，它的开发方式非常简单。
Webpart 和标准 asp 页面开发的问题在于，没有设计视图。
The best way i would say is to create a web user control and add that to a web part (a container webpart) - user controls can be added in the 12 hive and picked from there. I have tried that and its very easy way develop given that the page has a lot of contents.
Issue with Webpart and the standard asp page development is that, there's no design view.