有人想要一个Access Server吗？ [英] Anybody want an Access Server?
问题描述
我已经在商店里琢磨了一段时间的想法，如果有其他人有兴趣的话，我很好。
我正在考虑为Access MDB创建服务器实现。
这是一个相当直接的想法。服务器将是一个程序
，它会监听SQL命令，例如发送给它的SELECT或INSERT（通过TCP / IP）。反过来，它将针对
本地数据库运行SQL并返回记录（用于SELECT）或执行
信息（用于INSERT，UPDATE，DELETE）。 />
我认为我还可以实现虚拟
客户端上的记录集对象，可以进行检索，允许您编辑，转换为
UPDATE SQL，然后将其重新发送回服务器。这可以让你用相当容易和透明的对象工作
。
我还没有建造它，但我正在考虑它。还有其他人
可以用它吗？我知道我在某种程度上重塑了一个真正的
数据库，但在很多情况下，Access可以通过更多的连接来扩展它的实用性（和希望有更多的抗腐蚀性。
因为我是那些顽固的Access家伙之一，我知道我想要它是b $ b。
有什么想法吗？
-Ben
I''ve been tossing around an idea here in the shop for a while, and I am
curious if anyone else out there would be interested.
I am thinking of creating a server implementation for Access MDBs.
It''s a fairly straight-forward idea. The server would be a program
that would listen for SQL commands, such as SELECTs or INSERTs to be
sent to it (over TCP/IP). In turn, it would run the SQL against the
local database and return either records (for SELECT) or execution
information (for INSERT, UPDATE, DELETE).
I think that I could also implement a "virtual" recordset object on the
client end, which would retreive, allow you to edit, translate to
UPDATE SQL, and fire it back to the server. This would let you work
with the object fairly easily and transparently.
I haven''t built it yet, but I am thinking about it. Would anybody else
get any use out of it? I know that I am somewhat reinventing a "real"
database, but in many cases, Access could extend it''s usefulness with a
bit more connectivity (and hopefully a bit more corruption-resistance).
Since I''m one of those die-hard Access guys, I know that I would like
it.
Any thoughts?
-Ben
推荐答案
蚜虫，
你想写一个什么？这不是SQL Server& MSDE是？与
操作系统一起，良好的关系数据库引擎是更难以编码的编码之一。我坚定地在你决定建立之前先努力购买。营。我只是想知道你写的是什么
有足够的好处来说服我使用你的服务器而不是
微软的VB。净与& MSDE。
-
Alan Webb
kn ******* @ SPAMhotmail.com
这不是IT，它是'
< up ***@hotmail.com>在消息中写道
news：11 ********************* @ g14g2000cwa.googlegro ups.com ...
Uphid,
You want to write a what? Isn''t that what SQL Server & MSDE is? Along with
operating systems, a good relational database engine is one of the tougher
bits of coding to take on. I am firmly in the "try very hard to buy before
you decide to build" camp. I''d be interested just to see if what you write
has enough bang for the buck to persuade me to use your server instead of
Microsoft''s VB.Net & MSDE.
--
Alan Webb
kn*******@SPAMhotmail.com
"It''s not IT, it''s IS
<up***@hotmail.com> wrote in message
news:11*********************@g14g2000cwa.googlegro ups.com...
我已经在商店里讨论了一段时间的想法，如果有其他人有兴趣的话，我很好奇。
我在想创造Access MDB的服务器实现。
这是一个相当直接的想法。服务器将是一个程序，它将监听SQL命令，例如要发送给它的SELECT或INSERT（通过TCP / IP）。反过来，它将针对本地数据库运行SQL并返回记录（用于SELECT）或执行
信息（用于INSERT，UPDATE，DELETE）。
我认为我也可以实现一个虚拟的客户端上的记录集对象，可以进行检索，允许您编辑，转换为更新SQL，然后将其重新发送回服务器。这样可以让你轻松透明地使用对象。
我还没有构建它，但我正在思考它。其他任何人都可以使用吗？我知道我在某种程度上重塑了一个真正的数据库，但在很多情况下，Access可以通过更多的连接来扩展它的实用性（并且希望更具抗腐蚀性） 。
因为我是那些顽固的Access家伙之一，我知道我想要它。
有什么想法吗？
-Ben
I''ve been tossing around an idea here in the shop for a while, and I am
curious if anyone else out there would be interested.
I am thinking of creating a server implementation for Access MDBs.
It''s a fairly straight-forward idea. The server would be a program
that would listen for SQL commands, such as SELECTs or INSERTs to be
sent to it (over TCP/IP). In turn, it would run the SQL against the
local database and return either records (for SELECT) or execution
information (for INSERT, UPDATE, DELETE).
I think that I could also implement a "virtual" recordset object on the
client end, which would retreive, allow you to edit, translate to
UPDATE SQL, and fire it back to the server. This would let you work
with the object fairly easily and transparently.
I haven''t built it yet, but I am thinking about it. Would anybody else
get any use out of it? I know that I am somewhat reinventing a "real"
database, but in many cases, Access could extend it''s usefulness with a
bit more connectivity (and hopefully a bit more corruption-resistance).
Since I''m one of those die-hard Access guys, I know that I would like
it.
Any thoughts?
-Ben
嗯，我确实理解了诱惑，我曾经想过自己一次，但
唯一的原因我可以真正看到这样做是为了学习练习。
请记住，JET和MS SQL Server已经共享了很多逻辑，但是MS SQL
服务器还有轻量级MDSE版本，MSDE可以做一些适度的多线程，而JET则不行，这使得它更适合作为多个客户端的服务器
。 br />
2005年3月29日13:56:37 -0800， up *** @ hotmail.com 写道：
Well, I do understand the temptation, and I had that thought myself once, but
the only reason I can really see for doing it is as a learning exercise.
Remember that JET and MS SQL Server already share a lot of logic, but MS SQL
Server also has the light MDSE version, and MSDE can do some modest
multi-threading, while JET cannot, making it much more suitable as a server
for multiple clients.
On 29 Mar 2005 13:56:37 -0800, up***@hotmail.com wrote:
我在想创造Access MDB的服务器实现。
这是一个相当直接的想法。服务器将是一个程序，它将监听SQL命令，例如要发送给它的SELECT或INSERT（通过TCP / IP）。反过来，它将针对本地数据库运行SQL并返回记录（用于SELECT）或执行
信息（用于INSERT，UPDATE，DELETE）。
我认为我也可以实现一个虚拟的客户端上的记录集对象，可以进行检索，允许您编辑，转换为更新SQL，然后将其重新发送回服务器。这样可以让你轻松透明地使用对象。
我还没有构建它，但我正在思考它。其他任何人都可以使用吗？我知道我在某种程度上重塑了一个真正的数据库，但在很多情况下，Access可以通过更多的连接来扩展它的实用性（并且希望更具抗腐蚀性） 。
因为我是那些顽固的Access家伙之一，我知道我想要它。
有什么想法吗？
-Ben
I''ve been tossing around an idea here in the shop for a while, and I am
curious if anyone else out there would be interested.
I am thinking of creating a server implementation for Access MDBs.
It''s a fairly straight-forward idea. The server would be a program
that would listen for SQL commands, such as SELECTs or INSERTs to be
sent to it (over TCP/IP). In turn, it would run the SQL against the
local database and return either records (for SELECT) or execution
information (for INSERT, UPDATE, DELETE).
I think that I could also implement a "virtual" recordset object on the
client end, which would retreive, allow you to edit, translate to
UPDATE SQL, and fire it back to the server. This would let you work
with the object fairly easily and transparently.
I haven''t built it yet, but I am thinking about it. Would anybody else
get any use out of it? I know that I am somewhat reinventing a "real"
database, but in many cases, Access could extend it''s usefulness with a
bit more connectivity (and hopefully a bit more corruption-resistance).
Since I''m one of those die-hard Access guys, I know that I would like
it.
Any thoughts?
-Ben
up***@hotmail.com 写道：
我一直在商店里讨论一个想法，我很好奇，如果其他人有兴趣的话，我很好奇。 />
我正在考虑为Access MDB创建一个服务器实现。
这是一个相当直接的想法。服务器将是一个程序，它将监听SQL命令，例如要发送给它的SELECT或INSERT（通过TCP / IP）。反过来，它将针对本地数据库运行SQL并返回记录（用于SELECT）或执行
信息（用于INSERT，UPDATE，DELETE）。
我认为我也可以实现一个虚拟的客户端上的记录集对象，可以进行检索，允许您编辑，转换为更新SQL，然后将其重新发送回服务器。这样可以让你轻松透明地使用对象。
我还没有构建它，但我正在思考它。其他任何人都可以使用吗？我知道我在某种程度上重塑了一个真正的数据库，但在很多情况下，Access可以通过更多的连接来扩展它的实用性（并且希望更具抗腐蚀性） 。
因为我是那些顽固的Access人之一，我知道我想要它。
有什么想法吗？
I''ve been tossing around an idea here in the shop for a while, and I am
curious if anyone else out there would be interested.
I am thinking of creating a server implementation for Access MDBs.
It''s a fairly straight-forward idea. The server would be a program
that would listen for SQL commands, such as SELECTs or INSERTs to be
sent to it (over TCP/IP). In turn, it would run the SQL against the
local database and return either records (for SELECT) or execution
information (for INSERT, UPDATE, DELETE).
I think that I could also implement a "virtual" recordset object on the
client end, which would retreive, allow you to edit, translate to
UPDATE SQL, and fire it back to the server. This would let you work
with the object fairly easily and transparently.
I haven''t built it yet, but I am thinking about it. Would anybody else
get any use out of it? I know that I am somewhat reinventing a "real"
database, but in many cases, Access could extend it''s usefulness with a
bit more connectivity (and hopefully a bit more corruption-resistance).
Since I''m one of those die-hard Access guys, I know that I would like
it.
Any thoughts?
过去曾经发布过这个ng（wolfsomethingorother）的其他人告诉我们使用VB6建立一个使用VB6的Jet数据库的中间件tcp / ip链接。
。那时候没有多少兴奋。
Someone else who used to post to this ng (wolfsomethingorother) told of
building a middle ware tcp/ip link to a Jet database using VB6. Didn''t
raise to much excitement back then.
这篇关于有人想要一个Access Server吗？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
