SQL Server的最新客户端 [英] RADiest Client for SQL Server

查看:117
本文介绍了SQL Server的最新客户端的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我有一个SQL Server数据库。快要完成了。这将是一台

单一非联网机器。有一天有人可以通过

ADSL(可能是TS)访问它,但是现在它是单用户没有局域网。


机器将实际上是在运行MSDE。 Windows XP Home。


我现在非常高兴将所有业务逻辑放在SQL Server中。

触发器,SP等。


我已经获得了相当多的Access开发经验。


为此开发客户端的最快捷方式是什么? ?


MDB或ADP客户端?

OLE-DB或ODBC连接?

绑定或未绑定


我的体验是使用Access 97/2000 FE / BE类型的应用程序。


我有ADSL,客户有ADSL,所以任何紧急情况DBA类型的东西我

可以通过VNC做。


您的观点一如既往,最受重视和欢迎。


Mike

解决方案

" Mike MacSween" < MI ************************** @ btinternet.com>写在

消息新闻:41 ********************* @ news.aaisp.net.uk ...

为此开发客户的绝对最快方式是什么?


如果您的客户使用此应用程序,那么它应该是一个网页

应用程序。那不会是最神奇的,但可能是最合适的。

你的观点一如既往,最受重视和欢迎。




你可能不需要将这个帖子交给这么多团体,它真的是

打败了团队的目的。


Michael


" Michael C" < MC ***** @ NOSPAMoptushome.com.au>在消息中写道

news:O%**************** @ TK2MSFTNGP11.phx.gbl ...

" Mike MacSween < MI ************************** @ btinternet.com>在
消息新闻中写道:41 ********************* @ news.aaisp.net.uk ...

为此开发客户端的最快捷方式是什么?



如果您的客户使用此应用程序,那么它应该是一个web
应用程序。那不是最狂野的,但可能是最合适的。




谢谢。我不明白为什么它需要成为一个网络应用程序。一个用户使用数据库所在的机器

?我想要一个富客户端,而不是RSI诱导鼠标点击网页界面。

你的意见,如同最有价值和最受欢迎的。



你可能不需要将这个帖子交给这么多团体,它真的打败了成为团体的目的。 / blockquote>


也许。我没有太多的SQL服务器组经验。我没有确定最好的是什么。


干杯,迈克


MDB链接表格和绑定表格肯定是最好的b $ b快速开发可能:你只在安装时松动,

灵活性,速度,足迹,交易支持等。


(大卫)


" Mike MacSween" < MI ************************** @ btinternet.com>写在

消息新闻:41 ********************* @ news.aaisp.net.uk ...

我有一个SQL Server数据库。快要完成了。它将用于单个非联网机器。有一天,有人可能通过ADSL(可能是TS)访问它,但是现在它只是一个用户没有局域网。

机器实际上将运行MSDE。 Windows XP Home。

现在,我很高兴将所有业务逻辑放在SQL Server中。
触发器,SP等。

我已经获得了相当多的Access开发经验。

为此开发客户的绝对最快方式是什么?

MDB或ADP客户端?
OLE-DB或ODBC连接?
绑定或未绑定

我的体验是使用Access 97/2000 FE / BE类型的应用程序。

我有得到了ADSL,客户得到了ADSL,所以任何紧急的DBA类型的东西我都可以通过VNC来做。

你的意见一如既往地受到重视和欢迎。

迈克




I''ve got a SQL Server database. Nearly finished. It''s going to go on a
single non networked machine. One day somebody might get access to it over
ADSL (probably TS), but for now it''s a single user no lan.

The machine will actually be running the MSDE. Windows XP Home.

I''m quite happy, for now, to put all the business logic in SQL Server.
Triggers, SPs etc.

I''ve got a fair bit of Access development experience.

What''s the absolute quickest way to develop a client for this?

MDB or ADP client?
OLE-DB or ODBC connection?
Bound or unbound

My experience is with Access 97/2000 FE/BE type apps.

I''ve got ADSL, the customer''s got ADSL, so any emergency DBA type stuff I
can do via VNC.

Yours opinions, as ever, are most valued and welcome.

Mike

解决方案

"Mike MacSween" <mi**************************@btinternet.com> wrote in
message news:41*********************@news.aaisp.net.uk...

What''s the absolute quickest way to develop a client for this?
If this app is to be used by your clients then it should probably be a web
app. That''s not going to be the RADiest but possibly the most suitable.
Yours opinions, as ever, are most valued and welcome.



You probably didn''t need to cross post this to so many groups, it really
defeats the purpose of having groups.

Michael


"Michael C" <mc*****@NOSPAMoptushome.com.au> wrote in message
news:O%****************@TK2MSFTNGP11.phx.gbl...

"Mike MacSween" <mi**************************@btinternet.com> wrote in
message news:41*********************@news.aaisp.net.uk...

What''s the absolute quickest way to develop a client for this?



If this app is to be used by your clients then it should probably be a web
app. That''s not going to be the RADiest but possibly the most suitable.



Thanks. I don''t see why it needs to be a web app. One user using the machine
that the database lives on? I want a rich client for this, not RSI inducing
mouse clicking on a web interface.

Yours opinions, as ever, are most valued and welcome.



You probably didn''t need to cross post this to so many groups, it really
defeats the purpose of having groups.



Maybe. I''ve not got too much experience with the SQL server groups. I wasn''t
sure which the best were.

Cheers, Mike


MDB with linked tables and bound forms is surely the most
Rapid development possible: you loose only on Installation,
Flexibility, Speed, Footprint, Transactional support etc.

(david)

"Mike MacSween" <mi**************************@btinternet.com> wrote in
message news:41*********************@news.aaisp.net.uk...

I''ve got a SQL Server database. Nearly finished. It''s going to go on a
single non networked machine. One day somebody might get access to it over
ADSL (probably TS), but for now it''s a single user no lan.

The machine will actually be running the MSDE. Windows XP Home.

I''m quite happy, for now, to put all the business logic in SQL Server.
Triggers, SPs etc.

I''ve got a fair bit of Access development experience.

What''s the absolute quickest way to develop a client for this?

MDB or ADP client?
OLE-DB or ODBC connection?
Bound or unbound

My experience is with Access 97/2000 FE/BE type apps.

I''ve got ADSL, the customer''s got ADSL, so any emergency DBA type stuff I
can do via VNC.

Yours opinions, as ever, are most valued and welcome.

Mike




这篇关于SQL Server的最新客户端的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

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