这可行吗？ [英] Is this feasible?

问题描述

嗨


我们有一个具有前端/后端情况的访问桌面应用程序，其中所有

表都在后端和其他所有内容，表格/查询，在

前端。我们想创建一个Web应用程序来使用相同的访问数据库

，但担心能够处理Web应用程序用户的访问权限。将访问后端表移动到SQL Server并链接访问前端的

sql server表是否可行？b $ b是否可行？它将无法访问桌面

应用程序，因为所有处理仍将通过访问来完成，但Web应用程序可以

可能会受益于SQL Server上的表？然后随着时间的推移，我们

也可以重新编写访问桌面应用程序为原生sql。


谢谢


问候

解决方案

是，是的，是的......


你很聪明 - 这很好，提前思考似乎被高估了这个

主题，特别是在这个组中，因为有一些真正的mdb傻瓜

... :) （放轻松的家伙，只是在开玩笑，有点......）


链接表工作正常，你只会有点不舒服

确定你的数据类型都很好。此外，如果你依靠autonumbers

来关联表，你将需要转移那些在sql server中打开IDENTITY INSERT

的那些，无论你选择什么方法来移动数据使用

（DTS，BCP，VB代码/ ADO等，使用ADP进行复制和粘贴）。


我规定永远不要使用mdb'作为网络数据库后端的无数

问题文件锁定和其他问题（两者都有语法差异

和管理员认为Web文件夹应该只读），所以你可能

从那里拿走它。


祝你好运，我希望我能给你一些很好的信息 - 让我知道它是怎么回事

适合你？ :)


-

Jerry Boone

Analytical Technologies，Inc。
http://www.antech.biz

ASP，ASP的安全托管和开发解决方案。 NET，SQL Server和

访问

" John" <乔** @ nospam.infovis.co.uk>在消息中写道

新闻：3f ********************** @ news.dial.pipex.com。 ..

嗨

我们有一个具有前端/后端情况的访问桌面应用程序，其中所有
表都在后端和其他所有内容，表格/查询，在
前端。我们想制作一个使用相同访问数据库的Web应用程序，但担心能够处理Web应用程序用户的访问权限。将访问后端表移动到SQL Server并链接访问前端中的sql server表是否可行？它将无法访问桌面应用程序，因为所有处理仍将通过访问完成，但Web应用程序可能会受益于SQL Server上的表？然后随着时间的推移，我们还可以重新编写访问桌面应用程序作为本机sql。

感谢

问候

好吧，也许我是其中一个mdb boneheads根据Jerry的定义，但是很多成功或失败的Jet（请不要访问，请访问

不在网站上运行网站上的.MDB取决于你如何尝试使用它，以及访问的设计。有很多服务器

snobs周围也是，谁将这个工具归咎于自己的缺点。并且，

虽然我没有指责杰里这个，我不是在开玩笑说一下

吧。


Jet对于亚马逊来说不是一个好的引擎，但它对于具有适度的网站来说是一个非常有用且可靠的
可用引擎。用法。如果数据库和Jet与你的.asp页面相同的服务器和正确的设计/实现，那么你b / b
可能会获得比你的更好的性能。可比较的数量

在本地网络上的多用户环境中并发用户。


我不确定你的意思是什么语法差异 （与_what_？不同）。

当然，管理员认为网络文件夹应该只读不是与特定数据库相关的问题，而是与特定管理员相关的问题。

锁定问题，没有其他定义，听起来可能是

要求/设计/实施问题应该可以通过

小心注意来解决。


现在，所有这一切，这个特别是MDB骨头已经完成了他的大部分

支付Access客户端到各种服务器数据库后端的工作，因此对于这两种环境都有一些感觉。


Larry Linson

Microsoft Access MVP

" Jerry Boone" < JE *** @ antech.biz.killspam>在消息中写道

news：t8 ******************** @ newssvr11.news.prodigy .com ...

是的，是的，是的......

你很聪明 - 这很好，提前思考似乎在这个主题上被高估了，特别是在这个组中，因为有一些真正的mdb
骷髅... ...（简单的人，只是开玩笑，有点......）

链接表工作正常，你只会有点不舒服
确保您的数据类型都处于良好状态。此外，如果您依赖
自动编号关联表，则需要在sql server中打开IDENTITY INSERT
的那些，无论您选择哪种方法移动数据
（DTS， BCP，VB代码/ ADO等，使用ADP进行复制和粘贴）。

我做了一个规则，在文件锁定无数问题之后，永远不要使用mdb作为Web数据库后端和其他问题（两者都有语法差异
和管理员认为网页文件夹应该只读），所以你可以从那里拿走它。

祝你好运，我希望我给了你一些很好的信息 - 让我知道它为你带来了什么？ :)

- Jerry Boone
Analytical Technologies，Inc。
http://www.antech.biz
用于ASP，ASP.NET，SQL Server和
访问的安全托管和开发解决方案

John <乔** @ nospam.infovis.co.uk>在消息中写道
新闻：3f ********************** @ news.dial.pipex.com。 ..

嗨

我们有一个具有前端/后端情况的访问桌面应用程序，其中
所有表都在后端和其他所有表中，表格/查询，前端是
。我们希望创建一个Web应用程序以使用相同的访问
数据库，但担心能够处理Web应用程序用户的访问权限。是否可以将访问后端表移动到SQL Server并将
链接到访问前端的sql server表？它将无法访问
桌面应用程序，因为所有处理仍将通过访问完成，但Web应用程序可能会受益于SQL Server上的表？然后随着时间的推移
我们也可以重新编写访问桌面应用程序为原生sql。

感谢

问候

我听说每秒最多可达到10次点击


John Bickmore www.BicycleCam.com
www.Feed-Zone.com


" John" <乔** @ nospam.infovis.co.uk>在消息中写道

新闻：3f ********************** @ news.dial.pipex.com。 ..

嗨

我们有一个具有前端/后端情况的访问桌面应用程序，其中所有
表都在后端和其他所有内容，表格/查询，在
前端。我们想制作一个使用相同访问数据库的Web应用程序，但担心能够处理Web应用程序用户的访问权限。将访问后端表移动到SQL Server并链接访问前端中的sql server表是否可行？它将无法访问桌面应用程序，因为所有处理仍将通过访问完成，但Web应用程序可能会受益于SQL Server上的表？然后随着时间的推移，我们还可以重新编写访问桌面应用程序作为本机sql。

感谢

问候

Hi

We have an access desktop app with front-end/back-end situation where all
tables are in the back end and everything else, forms/queries, are in the
front end. We would like to make a web app to use the same access database
but are worried about access being able to handle web app users. Is it
feasible to move the access backend tables to the SQL Server and link the
sql server tables in the access front end? It will not help access desktop
app as all processing will still be done by access but the web app can
presumably benefit from tables being on the SQL Server? Then over time we
can also re-write the access desktop app to be native sql.

Thanks

Regards

解决方案

Yes, yes, yes...

You are smart - that''s good, thinking ahead seems to be overrated on this
subject, particularly in this group since there are some real mdb boneheads
around... :) (take it easy guys, just joking, kind of...)

Linking tables works fine, you will just have a little discomfort making
sure your datatypes are all in good shape. Also, if you rely on autonumbers
to relate tables, you will need to transfer those with IDENTITY INSERT
turned on within sql server, on whatever method you choose to move data with
(DTS, BCP, VB Code/ADO, etc, copy & paste using ADP).

I made a rule to never use mdb''s as web database backends after countless
problems with file locking and other problems (both with syntax difference
and admins who think web folders should be read only), so you can probably
take it from there.

Good luck, I hope I gave you some good information - let me know how it
turns out for you? :)

--
Jerry Boone
Analytical Technologies, Inc.
http://www.antech.biz
Secure Hosting and Development Solutions for ASP, ASP.NET, SQL Server, and
Access
"John" <Jo**@nospam.infovis.co.uk> wrote in message
news:3f**********************@news.dial.pipex.com. ..

Hi

We have an access desktop app with front-end/back-end situation where all
tables are in the back end and everything else, forms/queries, are in the
front end. We would like to make a web app to use the same access database
but are worried about access being able to handle web app users. Is it
feasible to move the access backend tables to the SQL Server and link the
sql server tables in the access front end? It will not help access desktop
app as all processing will still be done by access but the web app can
presumably benefit from tables being on the SQL Server? Then over time we
can also re-write the access desktop app to be native sql.

Thanks

Regards

Well, perhaps I am one of those "mdb boneheads" by Jerry''s definition, but a
great deal of the success or failure of a Jet (not Access, please, Access
isn''t running on the website) .MDB on a Web Site depends on how you try to
use it, and on the design of the accesses. There are a good many "server
snobs" around, too, who blame the tool for their own shortcomings. And,
while I''m not accusing Jerry of this, I am not joking one little bit about
it.

Jet wouldn''t be a good engine for Amazon, but it is a perfectly useful and
usable engine for sites with "modest" usage. If the database and Jet are on
the same server as your .asp pages, and proper design/implementation, you
are likely to get better performance than you would with a comparable number
of concurrent users in a multiuser environment over a local network.

I''m not sure what you mean by "syntax difference" (different from _what_?).
And certainly, "admins who think web folders should be read only" is not a
problem that is related to a particular database, but to particular admins.
"Locking issues", absent other definition, sounds like it might be a
requirements/design/implementation problem that ought to be fixable with
some careful attention.

Now, all that said, this particular "MDB bonehead" has done most of his
paying work on Access clients to various server DB back ends, so has some
feel for both environments.

Larry Linson
Microsoft Access MVP
"Jerry Boone" <je***@antech.biz.killspam> wrote in message
news:t8********************@newssvr11.news.prodigy .com...

Yes, yes, yes...

You are smart - that''s good, thinking ahead seems to be overrated on this
subject, particularly in this group since there are some real mdb boneheads around... :) (take it easy guys, just joking, kind of...)

Linking tables works fine, you will just have a little discomfort making
sure your datatypes are all in good shape. Also, if you rely on autonumbers to relate tables, you will need to transfer those with IDENTITY INSERT
turned on within sql server, on whatever method you choose to move data with (DTS, BCP, VB Code/ADO, etc, copy & paste using ADP).

I made a rule to never use mdb''s as web database backends after countless
problems with file locking and other problems (both with syntax difference
and admins who think web folders should be read only), so you can probably
take it from there.

Good luck, I hope I gave you some good information - let me know how it
turns out for you? :)

--
Jerry Boone
Analytical Technologies, Inc.
http://www.antech.biz
Secure Hosting and Development Solutions for ASP, ASP.NET, SQL Server, and
Access
"John" <Jo**@nospam.infovis.co.uk> wrote in message
news:3f**********************@news.dial.pipex.com. ..

Hi

We have an access desktop app with front-end/back-end situation where all tables are in the back end and everything else, forms/queries, are in the front end. We would like to make a web app to use the same access database but are worried about access being able to handle web app users. Is it
feasible to move the access backend tables to the SQL Server and link the sql server tables in the access front end? It will not help access desktop app as all processing will still be done by access but the web app can
presumably benefit from tables being on the SQL Server? Then over time we can also re-write the access desktop app to be native sql.

Thanks

Regards

i have heard access is good up to 10 hits per second

John Bickmore
www.BicycleCam.com
www.Feed-Zone.com

"John" <Jo**@nospam.infovis.co.uk> wrote in message
news:3f**********************@news.dial.pipex.com. ..

Hi

We have an access desktop app with front-end/back-end situation where all
tables are in the back end and everything else, forms/queries, are in the
front end. We would like to make a web app to use the same access database
but are worried about access being able to handle web app users. Is it
feasible to move the access backend tables to the SQL Server and link the
sql server tables in the access front end? It will not help access desktop
app as all processing will still be done by access but the web app can
presumably benefit from tables being on the SQL Server? Then over time we
can also re-write the access desktop app to be native sql.

Thanks

Regards

这篇关于这可行吗？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！