一个非常简单的应用程序的数据库是什么？ [英] What's a good database for a really simple app?

问题描述

我打算通过需要单个用户数据库的共享软件编写一个相当小的应用程序（VB2005）来分发

。我甚至不认为需要SQL Server Express版本，因为我认为它本质上是一个真正的DB，它一直在运行。


我真的需要像Access这样的东西并且正在考虑使用它

但是有很少的文档可以使用来自

DotNet的Access我不得不觉得这不是答案。两年前，Cor有一个

的例子，就是它。


所以，也许答案只是创建一个内存数据集并使用

根据需要，然后在完成后序列化并将其读回来需要

？这样的方法或其他方法有什么责任呢？

I''m planning on writing a fairly small app (VB2005) to be distributed
via shareware that needs a single user database. I don''t even think
that SQL Server Express edition is needed since I think that it is
essentially a true DB that runs all the time.

I really need something like Access and was thinking about using it
but there is so little documentation available on using Access from
DotNet that I have to feel that it is not the answer. Cor had an
example from two years back and that is about it.

So, perhaps the answer is just to create an in-memory dataset and use
it as needed, then serialize it when done and read it back in as
needed? What are the liabilities of an approach like this or some
other alternatives?

推荐答案

dgk写道：

我打算通过需要单个用户数据库的共享软件编写一个相当小的应用程序（VB2005）进行分发。我甚至不认为需要SQL Server Express版本，因为我认为它本质上是一个真正的DB，它一直在运行。

我真的需要一些东西喜欢Access并且正在考虑使用它
但是有很少的文档可以使用来自
DotNet的Access，我不得不觉得它不是答案。 Cor有一个两年前的例子，就是它。

所以，也许答案只是创建一个内存数据集并根据需要使用它，然后在完成后序列化并在需要时读回来？像这样或某些其他替代方法有什么责任？

I''m planning on writing a fairly small app (VB2005) to be distributed
via shareware that needs a single user database. I don''t even think
that SQL Server Express edition is needed since I think that it is
essentially a true DB that runs all the time.

I really need something like Access and was thinking about using it
but there is so little documentation available on using Access from
DotNet that I have to feel that it is not the answer. Cor had an
example from two years back and that is about it.

So, perhaps the answer is just to create an in-memory dataset and use
it as needed, then serialize it when done and read it back in as
needed? What are the liabilities of an approach like this or some
other alternatives?

有很多关于使用DotNet的Access的东西。主要的

差异只是连接字符串而你使用的是另一个

类。如果你觉得使用DotNet的SQL很舒服，那么使用Access

将是小菜一碟。


Chris

There is a ton of stuff about using Access from DotNet. The main
difference is just the connection string and you using a different
class. If you feel comfortable using SQL from DotNet, then using Access
will be a piece of cake.

Chris

我在小应用程序和访问数据库方面做了很多工作，并认为它可能是一个非常好的解决方案。

网上有很多关于VB.NET使用权限的例子。


" dgk" < dg*@somewhere.com>在消息中写道

news：53 ******************************** @ 4ax.com ...

I''ve done quite a lot with small apps and access databases and think its
probably a really good solution. There are plenty of examples out on the
net for use access from VB.NET.

"dgk" <dg*@somewhere.com> wrote in message
news:53********************************@4ax.com...

我打算通过需要单个用户数据库的共享软件编写一个相当小的应用程序（VB2005）来分发。我甚至不认为需要SQL Server Express版本，因为我认为它本质上是一个真正的DB，它一直在运行。

我真的需要一些东西喜欢Access并且正在考虑使用它
但是有很少的文档可以使用来自
DotNet的Access，我不得不觉得它不是答案。 Cor有一个两年前的例子，就是它。

所以，也许答案只是创建一个内存数据集并根据需要使用它，然后在完成后序列化并在需要时读回来？这种方法或其他替代方案的责任是什么？

I''m planning on writing a fairly small app (VB2005) to be distributed
via shareware that needs a single user database. I don''t even think
that SQL Server Express edition is needed since I think that it is
essentially a true DB that runs all the time.

I really need something like Access and was thinking about using it
but there is so little documentation available on using Access from
DotNet that I have to feel that it is not the answer. Cor had an
example from two years back and that is about it.

So, perhaps the answer is just to create an in-memory dataset and use
it as needed, then serialize it when done and read it back in as
needed? What are the liabilities of an approach like this or some
other alternatives?

On Tue，2006年1月3日10:40:32 -0500 ，我不喜欢垃圾邮件< [e-mail]>

写道：

On Tue, 03 Jan 2006 10:40:32 -0500, I Don''t Like Spam <[e-mail]>
wrote:

dgk写道：

I 我计划通过需要单个用户数据库的共享软件来编写一个相当小的应用程序（VB2005）。我甚至不认为需要SQL Server Express版本，因为我认为它本质上是一个真正的DB，它一直在运行。

我真的需要一些东西喜欢Access并且正在考虑使用它
但是有很少的文档可以使用来自
DotNet的Access，我不得不觉得它不是答案。 Cor有一个两年前的例子，就是它。

所以，也许答案只是创建一个内存数据集并根据需要使用它，然后在完成后序列化并在需要时读回来？像这样或某些其他替代方法有什么责任？

I''m planning on writing a fairly small app (VB2005) to be distributed
via shareware that needs a single user database. I don''t even think
that SQL Server Express edition is needed since I think that it is
essentially a true DB that runs all the time.

I really need something like Access and was thinking about using it
but there is so little documentation available on using Access from
DotNet that I have to feel that it is not the answer. Cor had an
example from two years back and that is about it.

So, perhaps the answer is just to create an in-memory dataset and use
it as needed, then serialize it when done and read it back in as
needed? What are the liabilities of an approach like this or some
other alternatives?

有很多关于使用DotNet的Access的东西。主要的区别只是连接字符串和你使用不同的类。如果您觉得使用DotNet中的SQL感觉很舒服，那么使用Access
将是一块蛋糕。

Chris

There is a ton of stuff about using Access from DotNet. The main
difference is just the connection string and you using a different
class. If you feel comfortable using SQL from DotNet, then using Access
will be a piece of cake.

Chris

其实关键点是从

DotNet创建Access数据库 - 这就是没有太多文档的内容。我不想要b $ b想要运送一个空的数据库;如果它不存在那么我想

即时创建它。我用VB6做了一段时间。对于DotNet，

Cor'的例子需要引用ADOX ext 2.0和：


Dim catNewDB作为新的ADOX.Catalog

catNetDB.Create（" Provider = Microsoft ...

我想我会尝试它，如果它仍然有用（例子是两年后）

之前）我想我可以做到。我希望安装向导和ClickOnce

可以应对挑战。


只需创建一个DB在内存中并序列化它仍然很诱人。

Actually the sticking point was CREATING an Access database from
DotNet - that''s what there isn''t much documentation about. I don''t
want to ship an empty database; if it doesn''t exist then I want to
create it on the fly. I did it using VB6 a while back. For DotNet,
Cor''s example requires a reference to ADOX ext 2.0 and:

Dim catNewDB as New ADOX.Catalog
catNetDB.Create("Provider=Microsoft ...

I guess I try it and if it still works (the example is from two years
ago) then I guess I can do it. I hope the Install Wizard and ClickOnce
is up to the challenge.

The idea of just creating a DB in memory and serializing it is still
tempting though.

这篇关于一个非常简单的应用程序的数据库是什么？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！