不同的类型转换A2k和A97？ [英] Different type conversion A2k and A97 ?
问题描述
大家好，
我有一个数据库，我需要在不同版本的Access中使用。
这是大多数地方的A97和其他几个地方的A2k 。
（我在A97中开发并将db转换为A2k用于其他这些位置）
FYI：我使用A97作为两个版本的后端。没问题。
转换后A97> A2k所有（似乎）工作都很好，除了我今天才发现的一件事。
使用未绑定的表单来收集追加查询A2k中使用的数据会因appendquery失败。
它始终有效并且仍在A97中运行。
顺便说一句：在这个例子中，我使用的是本地表追加。
问题似乎是Access无法理解未绑定表单中的值。
Access抱怨类型转换错误。
当我在设计视图中查看查询并将视图切换到要追加的记录时，我会在数据网格中看到类似=的奇怪字符。
解决方案：
当我更改查询并为*每个字段*添加参数，使其按预期工作。
但是必须为所有字段添加参数（27）非常烦人...
另外：我很害怕我现在必须检查所有这些查询... Aarrrrrgggghhhh。
有何评论？这里没有腐败AFAIK。
谢谢，
Arno R
>当我更改查询并为表格中的*每个字段*添加参数时，工作
是
但是必须添加所有字段的参数（27）非常烦人...
是
另外：我很害怕我必须检查所有这些查询''现在......
Aarrrrrgggghhhh。
是
<任何意见？这里没有腐败AFAIK。
有时甚至添加参数类型是不够的。幸运的是，
我们已经为大多数参数查询提供了参数类型，
以及无论如何它失败并且崩溃了A2000的几个案例，
我们能够编写解决方案。
（大卫）
Arno R < AR *********** @ tiscali.nl>在消息中写道
news：43 ********************** @ text.nova.planet.nl。 ..
大家好，
我有一个数据库需要在不同版本的Access中使用。
这是大多数地方的A97和其他几个地方的A2k一样。
（我在A97中开发并将db转换为A2k用于其他这些位置）
FYI：我使用A97作为后端版本。没问题。
转换后A97> A2k所有（似乎）工作都很好，除了
我今天才发现的一件事。
使用未绑定的表单收集用于appendquery A2k
因附加查询而失败。
它始终有效并且仍在A97中运行。
Btw：在这个例子中我使用的是本地要追加的表格。
问题似乎是Access无法理解
未绑定表单中的值。
Access抱怨类型转换错误。
当我在设计视图中查看查询并将视图切换到要添加的记录
时，我会在数据网格中看到奇怪的字符，如= 。
解决方案：
当我更改查询并为*每个字段*添加参数时，
按预期工作。 />
但是必须为所有字段添加参数（27）非常烦人...
另外：我很害怕我现在必须检查所有这些查询。 。
Aarrrrrgggg嗯。
有何评论？这里没有腐败AFAIK。
谢谢，
Arno R
" david epsom dot com dot au" <大卫@ epsomdotcomdotau> schreef在bericht新闻：43 *********************** @ lon-reader.news.telstra.net ...
有时甚至添加参数类型是不够的。幸运的是，
我们已经为大多数参数查询提供了参数类型，
以及无论如何它都失败并且崩溃了A2000的几个案例，我们能够编写解决方案。
（大卫）
谢谢David，
我用Google搜索这个问题并在Allen Browne的网站上看到了关于设置未绑定控件的格式属性的提示。
但是这也没有运气。在我的示例中，Access''想要'''是所有字段的参数设置。
我确实读到Jet 3.6和Jet 4.xxx在这个''类型猜测'中有区别'问题。
您是否知道在A2002或A2003中这个问题是否已解决？
Arno R
Arno R写道：
问题似乎是Access不明白未绑定表单中的值。
访问抱怨类型转换错误。
当我在设计视图中查看查询并将视图切换到要追加的记录时，我在数据网格中看到类似=的奇怪字符。
如果我们知道Access如何被要求理解
未绑定表单中的值以及何时以及何种类型的值，它将会很有帮助。一些
行代码可以显示这个？
有何评论？这里没有腐败AFAIK。
表单上的所有数据都是字符串，字节序列。根据情况和你的观点，神奇地访问或
邪恶地，可能会将这些视为其他东西：数字，布尔，blob等等。
随着Access和VBA的进展，他们似乎将更多的
功能与unicode合并。这可能会导致我们设计的一些东西需要自我毁灭。我们的工作预期在一个字节之前现在是
得到两个。
这可能与你的问题无关，当然，
更多信息可以帮助我理解。
Hi all,
I have a database that I need to use in different versions of Access.
This is A97 in most places and A2k in a few other locations.
(I develop in A97 and convert the db to A2k for these other locations)
FYI: I am using A97 as backend for both versions. No problem.
After conversion A97 > A2k everything (seems to) work(s) just fine, except for one thing I only discovered today.
Using an unbound form to collect data that is used in an appendquery A2k fails with the appendquery.
It always worked and still works in A97.
Btw: In this example I am using a local table to append to.
Problem seems to be that Access does not understand the values in the unbound form.
Access complains about type conversion errors.
When I look at the query in design view and switch the view to the records to be appended I see strange characters like = in the datagrid.
Solution:
When I change the query and add parameters for *each field* in the form it works as expected.
But having to add parameters for all the fields (27) is very annoying...
Also: I am aftraid I have to check all these query''s now ... Aarrrrrgggghhhh.
Any comments? No corruption here AFAIK.
Thanks,
Arno R
> When I change the query and add parameters for *each field* in the form itworks
Yes
But having to add parameters for all the fields (27) is very annoying...
Yes
Also: I am aftraid I have to check all these query''s now ...
Aarrrrrgggghhhh.
Yes
< Any comments? No corruption here AFAIK.
Sometimes even adding parameter types isn''t enough. Fortunately,
we already had parameter types for most of our parameter queries,
and for the few cases where it failed anyway and crashed A2000,
we were able to code work-arounds.
(david)
"Arno R" <ar***********@tiscali.nl> wrote in message
news:43**********************@text.nova.planet.nl. ..
Hi all,
I have a database that I need to use in different versions of Access.
This is A97 in most places and A2k in a few other locations.
(I develop in A97 and convert the db to A2k for these other locations)
FYI: I am using A97 as backend for both versions. No problem.
After conversion A97 > A2k everything (seems to) work(s) just fine, except
for one thing I only discovered today.
Using an unbound form to collect data that is used in an appendquery A2k
fails with the appendquery.
It always worked and still works in A97.
Btw: In this example I am using a local table to append to.
Problem seems to be that Access does not understand the values in the
unbound form.
Access complains about type conversion errors.
When I look at the query in design view and switch the view to the records
to be appended I see strange characters like = in the datagrid.
Solution:
When I change the query and add parameters for *each field* in the form it
works as expected.
But having to add parameters for all the fields (27) is very annoying...
Also: I am aftraid I have to check all these query''s now ...
Aarrrrrgggghhhh.
Any comments? No corruption here AFAIK.
Thanks,
Arno R
"david epsom dot com dot au" <david@epsomdotcomdotau> schreef in bericht news:43***********************@lon-reader.news.telstra.net...
Sometimes even adding parameter types isn''t enough. Fortunately,
we already had parameter types for most of our parameter queries,
and for the few cases where it failed anyway and crashed A2000,
we were able to code work-arounds.
(david)
Thanks David,
I Googled around for this problem and saw a tip on Allen Browne''s site about setting the format property for unbound controls.
But no luck with this also. In my example Access ''want''s'' a parameter setting for all fields.
I did read that there is a difference between Jet 3.6 and Jet 4.xxx in this ''type guessing'' issue.
Do you happen to know whether this ''problem'' is ''solved'' in A2002 or A2003?
Arno R
Arno R wrote:
Problem seems to be that Access does not understand the values in the unbound form.
Access complains about type conversion errors.
When I look at the query in design view and switch the view to the records to be appended I see strange characters like = in the datagrid.
It woud be helpful if we knew how Access is being asked to "understand"
the values in the unbound form and when and what types of values. A few
lines of code could show this?
Any comments? No corruption here AFAIK.
All data on form are strings, series of bytes. Access magically or
wickedly, depending upon the situation and your point of view, may
treat these as someting else: numbers, booleans, blobs whatever.
As Access and VBA progress they seem to merge more of their
functionality with unicode. This can cause some things we have designed
to self-destruct. Where our work expected one byte previously it is now
getting two.
This may have nothing to do with your problem whatever, of course,
More information would help me to understand.
这篇关于不同的类型转换A2k和A97？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
