OT支持应用程序 [英] OT Supporting an application
问题描述
我有一个用MS-Access编写的应用程序。这是一个完整的
应用程序，用于管理企业的日常运营。
该程序已准备好在其他客户站点中使用。
我想知道你是否有任何关于支持申请的建议。
既然它从来没有任何外界曝光，我不会希望是
赚取大量销售而不能支持出现的问题。
我相信因为与一小部分公司合作扭结，它
可以发布给更多公司。我根本不想要一堆销售但没有办法处理客户支持问题。
我也知道购买它的公司将为
增强功能提出建议。其他人可能需要一些超出核心程序范围的自定义编程。
所以我需要提供技术支持和其他编程。
我的问题是一个人可以合理地支持多少家公司？
我不是在寻找一个坚定的人物，更多的是关于什么是哎呀我是b / b
让自己进入。没有销售，我再也买不起另一个b $ b程序员了。我想知道是否有断点或里程碑
，你需要扩展和雇用更多的人。
如果您参与或采用了从概念到软件的软件程序/>
销售，如果你能分享一些你的经验知识，我将不胜感激。
I have an application written in MS-Access. It is a complete
application that manages the day-to-day operations of a business.
The program is nearly ready to be used in other customer sites.
I am wondering if any of you have advice on supporting an application.
Since it has never had any outside exposure, what I don''t want is to
make a bunch of sales and not be able to support the issues that arise.
I believe as kinks are worked out with a smaller set of companies, it
can be released to more companies. I simply don''t want to have a bunch
of sales but no means to handle customer support problems.
I also know that companies that purchase it will make suggestions for
enhancements. Others may need some custom programming beyond the scope
of the core program.
So I will need to supply tech support and also additional programming.
My question is "How many companies can 1 person reasonably support?"
I''m not looking for a firm figure, more an idea of what the heck I''m
getting myself into. Without a sale yet, I can''t afford another
programmer. I''m wondering if there are "breakpoints" or milestones
where you need to expand and hire more people.
If you''ve been involved with or taken a software program from concept to
sales, I''d appreciate it if you''d share some knowledge of your experiences.
推荐答案
沙拉，恭喜你到达你申请的地方
可以销售。
希望你会得到几个回复，你可以获得
$ b的好处$ b每个人的经历。
假设你在编程方面做得很好，而且没有很多
的销售经验和营销，我怀疑你有太多担心
关于这里。销售将慢慢发生。您将获得
反馈的好处，以增强您的应用程序。当你有几十个b
的客户支持时，你将拥有一个好的，稳定的软件，
可以像用户期望的那样工作。
希望您已经考虑了如何收取支持费用（每月定期
费用，或
Salad, congratulations on getting to the place where your application is
marketable.
Hopefully you will get several responses, where you gain the benefit of
everyone''s experiences.
Assuming that you have done a good job with programming, and don''t have lots
of experience with sales and marketing, I doubt you have too much to worry
about here. Sales will happen slowly enough. You will have the benefit of
feedback to enhance your application. By the time you have dozens of
customers to support, you will have a good, stable piece of software that
works as users expect.
Hopefully have have considered how you charge for support (regular monthly
fee, or
/ hr。）
无论你有多好，还会有一些不相关的支持
用户的问题，例如为什么你的节目不接受2月31日？或者
我的报告去过哪台打印机？或为什么我的鼠标不工作？由于
Access被很多人在企业数据库环境之外使用，
其中一些用户没有任何人可以提出基本的东西，比如如何
在他们的计算机上设置日期。
其他一些建议可以帮助支持：
1.记录错误
用户不会阅读错误消息，也无法告诉您发生了什么。简单的
错误记录让你知道错误是什么，什么时候发生，它发生了什么，b $ b发生了什么，以及它多久发生一次。您甚至可能希望包含一个
命令按钮，用于打印或通过电子邮件发送错误日志报告，以便用户可以将b $ b发送给您。示例：
http://allenbrowne.com/ser-23a.html
2.考虑记录基本记录信息
我创建的每个表格都会粘贴4个附加字段，以记录谁
创建了记录以及何时，谁最后更新记录以及何时。
如果没有这个，你就无法验证你的应用程序是否正常工作或
not 。用户会问你，为什么上个月没有订购999的发票？如果
您可以证明订单999实际上是在1月3日输入的，并且他们
在1月2日生成了12月的发票，您可以对它感到满意
不是您的发票生成例程的错误。相反，如果没有输入或修改记录
，你已经向自己证明了你需要解决的
a bug。
3.版本信息
对于远程支持，您需要提供一个用户可以阅读的屏幕
版本详细信息：
- 你的软件
- 办公服务包
- JET服务包
以及关于它们连接到哪个后端的基本信息。 （不要嘲笑：用户将连接到备份，然后问你为什么他们的数据是否与其他人的数据不一致。）
示例：
http://allenbrowne.com/ ser-53.html
-
Allen Browne - 微软MVP。西澳大利亚珀斯
访问用户提示 - http：// allenbrowne .com / tips.html
回复群组，而不是mvps dot org的allenbrowne。
" salad" < cu ***** @ george.comwrote in message
news：0v ****************** @ newsread2.news.pas。 earth link.net ...
/hr when needed.)
No matter how good you are, there will also be some irrelevant support
questions from users, e.g. "Why won''t your program accept Feb 31?", or
"Which printer did my report go to?" or "Why isn''t my mouse working?" Since
Access is used by lots of people outside corporate database environments,
some of these users don''t have anyone they can ask basic things like how to
set the date on their computer.
Some other suggestions to help with support:
1. Log errors
Users do not read error messages, and can''t tell you what happened. Simple
error logging lets you know what the error was, when it happened, who it
happened to, and how often it recurred. You may even want to include a
command button that prints or emails the error log report so the user can
send it to you. Example:
http://allenbrowne.com/ser-23a.html
2. Consider recording basic record info
Every table I create gets 4 additional fields pasted in, to record who
created the record and when, and who last updated the record and when.
Without this, you can''t verify if your application is working correctly or
not. Users will ask you, "Why didn''t order 999 get invoiced last month?" If
you can demonstrate that order 999 was actually entered on Jan 3rd, and they
generated the December invoices on January 2, you can be satisfied that it
is not a bug with your invoice generating routine. Conversely, if the record
has not been entered or modified, you have proved to yourself that there is
a bug you need to solve.
3. Version info
For remote support, you need to provide a screen where the user can read you
version details on:
- your software
- Office service packs
- JET service packs
as well as basic info about which back end they are connected to. (Don''t
laugh: users will connect to a backup, and then ask you why their data is
not consistent with everyone else''s.)
Example:
http://allenbrowne.com/ser-53.html
--
Allen Browne - Microsoft MVP. Perth, Western Australia
Tips for Access users - http://allenbrowne.com/tips.html
Reply to group, rather than allenbrowne at mvps dot org.
"salad" <cu*****@george.comwrote in message
news:0v******************@newsread2.news.pas.earth link.net...
>我有一个用MS-Access编写的应用程序。它是一个完整的应用程序，用于管理企业的日常运营。
该程序已准备好在其他客户站点中使用。
我想知道你是否有任何关于支持申请的建议。
既然它从来没有任何外部曝光，我不想要的是制作
a一堆销售而且无法支持出现的问题。
我相信因为与一小部分公司合作扭结，它可以
将发布给更多公司。我只是不想有一堆
销售，但没有办法处理客户支持问题。
我也知道购买它的公司将为
增强功能提出建议。其他人可能需要一些超出核心计划范围的自定义编程。
所以我需要提供技术支持和其他编程。
我的问题是一个人可以合理地支持多少家公司？我不是在寻找一个坚定的人物，而是更多地了解我自己得到了什么。没有销售，我买不起另一个程序员。我是b / b
想知道是否有断点或者你需要的里程碑
扩展和雇用更多的人。
如果您参与或采用了从概念到软件的软件程序$>
销售，如果您分享一些关于
体验的知识，我将不胜感激。
>I have an application written in MS-Access. It is a complete application
that manages the day-to-day operations of a business.
The program is nearly ready to be used in other customer sites.
I am wondering if any of you have advice on supporting an application.
Since it has never had any outside exposure, what I don''t want is to make
a bunch of sales and not be able to support the issues that arise.
I believe as kinks are worked out with a smaller set of companies, it can
be released to more companies. I simply don''t want to have a bunch of
sales but no means to handle customer support problems.
I also know that companies that purchase it will make suggestions for
enhancements. Others may need some custom programming beyond the scope of
the core program.
So I will need to supply tech support and also additional programming.
My question is "How many companies can 1 person reasonably support?" I''m
not looking for a firm figure, more an idea of what the heck I''m getting
myself into. Without a sale yet, I can''t afford another programmer. I''m
wondering if there are "breakpoints" or milestones where you need to
expand and hire more people.
If you''ve been involved with or taken a software program from concept to
sales, I''d appreciate it if you''d share some knowledge of your
experiences.
Allen Browne写道：
Allen Browne wrote:
沙拉，祝贺你到达申请地点
适销对路。
Salad, congratulations on getting to the place where your application is
marketable.
你好。谢谢你的客气话。
Hi Allen. Thank you for your kind words.
希望你会得到几个回复，你可以从中获得每个人的经验。
每个人的经历。
Hopefully you will get several responses, where you gain the benefit of
everyone''s experiences.
我也希望如此。
I''m hoping so too.
假设你在编程方面做得很好，并且没有
有很多销售和营销经验，我怀疑你有太多的担心在这里担心。销售将慢慢发生。您将获得
反馈的好处，以增强您的应用程序。当你有几十个客户需要支持时，你将获得一个好的，稳定的
软件，可以按照用户的期望工作。
Assuming that you have done a good job with programming, and don''t have
lots of experience with sales and marketing, I doubt you have too much
to worry about here. Sales will happen slowly enough. You will have the
benefit of feedback to enhance your application. By the time you have
dozens of customers to support, you will have a good, stable piece of
software that works as users expect.
这正是我/我所在的地方。好节目，小营销
经验。我预计最初的销售会很慢。我认为每次销售都会产生价值，然后我就可以解决这些问题。
下个月，该计划将获得产品创新奖。 />
来自该行业的一个组织。我预计奖励将会产生一些兴趣。
That is exactly what/where I am. Good program, little marketing
experience. I expect sales to be slow initially. I figure that for
each sale, kinks will be exposed which I can then remove.
Next month the program will receive the award for product innovation
from one of the industry''s organizations. I anticipate the award will
generate some interest.
希望你已经考虑了如何收取支持费用（常规
月费，或
Hopefully have have considered how you charge for support (regular
monthly fee, or
这篇关于OT支持应用程序的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
