帮助处理字符串长度溢出? [英] Help handling string length overflow?

查看:167
本文介绍了帮助处理字符串长度溢出?的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我有一个表单,用户将手写合同复制到文本

字段Contract1中。

合同通常会导致255个字符。

因此,我提供了Contract2,Contract3和Contract4。字段。

当Contract1时不能接受进一步的输入,用户继续

Contract2,等等。

由于显而易见的原因,我不想使用备忘录字段。


有没有人有一个事件程序和代码,可以监控

打字并以编程方式将文本从最后一次回归中移回

" Contract2"。


任何帮助真心感谢

I have a form where the user copies a handwritten contract into a text
field "Contract1".
The contract usually exeeds 255 characters.
Therefore I provided "Contract2", "Contract3", and "Contract4" fields.
When "Contract1" cannot accept further input, the user continues on to
"Contract2", ect.

I don''t want to use memo fields for obvious reasons.

Does anyone have an event procedure and code, which could monitor
typing and programatically move text from the last cariage return to
"Contract2".

Any help sincerely appreciated

推荐答案

wo ******** @ comcast.net 写道:
wo********@comcast.net wrote:
我有一个表格,用户将手写合同复制到文本
字段Contract1。
合同通常会输出255个字符。
因此我提供了Contract2, Contract3"和" Contract4"字段。
当Contract1时不能接受进一步的输入,用户继续使用
Contract2,等等。

出于显而易见的原因,我不想使用备忘录字段。
有没有人有一个事件程序和代码,可以监控
打字并以编程方式将文本从最后一次返回到
Contract2。

任何帮助真诚地感谢
I have a form where the user copies a handwritten contract into a text
field "Contract1".
The contract usually exeeds 255 characters.
Therefore I provided "Contract2", "Contract3", and "Contract4" fields.
When "Contract1" cannot accept further input, the user continues on to
"Contract2", ect.

I don''t want to use memo fields for obvious reasons.

Does anyone have an event procedure and code, which could monitor
typing and programatically move text from the last cariage return to
"Contract2".

Any help sincerely appreciated



好​​吧,你有没有考虑让这个领域成为一个备忘录领域?


这听起来很低效。为什么不将合同扫描到一个文件

并提供一个链接。


Well, have you considered making the field a memo field?

This sounds so inefficient tho. Why not scan the contract in to a file
and provide a link to it.


手写合同。

我指出,出于显而易见的原因,我不想使用备忘录字段。

Handwritten contracts.
I don''t want to use memo fields for obvious reasons as you point out.


wo ******** @ comcast.net 写道:
wo********@comcast.net wrote:
手写合同。
我不喜欢当你指出时,出于显而易见的原因,我不想使用备忘录字段。
Handwritten contracts.
I don''t want to use memo fields for obvious reasons as you point out.



哦。我忽略了你的声明,你不想使用备忘录字段。


你可以看到最大的合同是什么。然后创建一大堆

字段来持有最长的合约。创建一个包含255

字符的输入掩码,当该人遇到限制陷阱时,表单''OnError

事件并转到下一个字段。


如果我有兴趣做你正在尝试的事情(而且我永远不会b / b
)我会创建一个单独的表,其中包含一个指向该键的链接和一个

合同文本字段。现在我将合同字段设为子表单,并将

循环设置为AllRecords。它将被视为主要的b / b
比例。编辑合同将是屁股中的一个主要痛苦。

如果你删除了单词或短语,它不会自动重新格式化,但是上帝不会使用备忘录来b / b
如果你到现场结束时还有
,你会去下一张唱片。



Oh. I overlooked your statement you don''t want to use a memo field.

You could see what the largest contract is. Then create a whole slew of
fields to hold the longest contract. Create an input mask with 255
characters and when the person hits the limit trap the form''s OnError
event and go to the next field.

If I had any inclination to do what you are attempting (and I never
would) I would make a separate table with a link to the key and a
contract text field. Now I''d make the contract field(s) a subform with
Cycle set to AllRecords. It would be considered a kludge of major
proportions. Editting the contract would be a major pain in the ass.
It wouldn''t automatically reformat if you deleted words or phrases, but
by God it would not use memos and you''d go to the next record if you got
to the end of the field.



这篇关于帮助处理字符串长度溢出?的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆