是否需要在女士访问中定义关系? [英] Is it necessary to define relationships in Ms access?

问题描述

我开发Access数据库. 开发完成后，所有访问数据库都使用ODBC DSN文件链接到MS SQL Server和postgres服务器.

很多时候，我会在前端运行查询，但有时我会进行后端查询，以使服务器完成艰苦的工作.

我想知道是否有必要在功能区的数据库工具"选项卡中创建关系.我知道使用查询设计对话框时，它会使开发变得更容易，并且我知道任何MS Access计算机课程都可以教您制作它们，但是除此之外，还有什么意义呢?它会加快查询速度吗?是像注释代码这样的惯例/礼节吗?

解决方案

将表放在ODBC后端中，在Access前端中定义关系的唯一直接原因是在查询设计器中预定义JOIN的便利. >

在大型应用程序中，这对我来说足够了.

当然，它将帮助在前端开发的其他任何人了解表关系.

顺便说一句，当PostgreSql成为生产数据库时，为什么要用SQL Server开发?不要低估SQL方言之间的差异(因为您还使用了后端查询，也可能使用了存储过程).

I develop Access Databases. All access databases use an ODBC DSN file link to a MS SQL Server and a postgres server once development is complete.

Many times I will run queries on the front end, but occasionally I will make back end queries to make the servers do the hard work.

I am wondering if it is necessary to create relationships in the Database Tools tab in the ribbon. I know it makes developing easier from time to time when using the query design dialogue and I know any MS Access computer class will teach you to make them, but aside from that what is the point? Does it speed up queries? Is it a convention/etiquette thing like commenting your code?

解决方案

With your tables in an ODBC backend, the only direct reason to define relationships in the Access frontend is the convenience to have JOINs predefined in the query designer.

In a large-ish application, that's reason enough for me.

And of course, it will help anyone else who will develop in the frontend to understand the table relations.

BTW, why do you develop with SQL Server when PostgreSql will be the production database? Don't underestimate the differences between the SQL dialects (since you also use backend queries and maybe stored procedures).

这篇关于是否需要在女士访问中定义关系?的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！