在运行时版本(accde)中操作报表定义 [英] Manipulating Report Definitions in a runtime-version (accde)

查看:104
本文介绍了在运行时版本(accde)中操作报表定义的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

您好,我是具有SQL-Server后端的访问应用程序的主要开发人员。

Hello, I am the main developer of an access application with a SQL-Server backend.

然而,我的客户的一些用户必须使用自定义查询和报告来增强前端。他们必须在自己的本地前端版本中开发和测试他们的对象。为所有用户部署新的/更改的对象很复杂。我花了
他们的版本并在我当前的开发版本中手动集成它并将副本分发给所有用户。随着越来越多的开发人员这种方式对我来说变得越来越烦人和不安全。



我的想法是在服务器上集成一种存储库。

我将使用

Application.LoadFromText acQuery,..........
$
Application.LoadFromText acReport

resp。 SaveToText

并管理SQL-Server上的文件。



使用合适的逻辑,这对于安装了Access的accdb版本非常完美。

问题是某些用户必须只使用运行时版本(accde)。当然,运行时版本的概念是隐藏代码并防止用户更改软件。不过我可以使用"LoadFromText"。查询没有问题。
对于报告,这不起作用 - 通过访问阻止他们进行更改!  

是否有其他方法可以在运行时版本中导入报告???



$

Nevertheless some users of my customer must enhance the frontend with custom querys and reports. They must develop and test their objects in their own local frontend version. The deployment of the new/changed objects for all users is complicated. I take their version and integrate it by hand im my current develpement version and distribute a copy to all users. With the increasing numbers of develper this way becomes more and more annoying and unsecure for me.

My idear is to integrate a kind of repository on the server.
I will use
Application.LoadFromText acQuery, ..........
Application.LoadFromText acReport
resp. SaveToText
and manage the files on the SQL-Server.

With a suitable logic this works very perfect for the accdb Version with installed Access.
The problem is that some users must use only the runtime version (accde). Of course the concept of the runtime-version is to hide the code and prevent the user from changing the sofware. Nevertheless I can use "LoadFromText" for query without problems. For reports this does not work - they are blocked for changes by access !?  
Is there an other way to import reports in the run-time version ???


推荐答案


是否有其他方法可以在运行时版本中导入报告???

Is there an other way to import reports in the run-time version ???

嗨Andreas,

所有这些在很大程度上取决于用户想要/需要的灵活性。

All depends very much on the flexibility the users want/need.

可能我的工作方式与你的完全不同,我不要使用Access报告,而是使用构建块直接创建rtf或html文档。

Probably my way of working is completely different from yours, I don't use Access reports, but use building blocks to create directly rtf- or html-documents.

在我的所有应用程序中,用户不会修改任何代码(就像运行时版本一样)。用户的灵活性是他可以"撰写"。他自己的字段,WHERE子句和ORDER BY子句的sql-string,甚至(在这个
时刻的限制)表。

In all my applications users don't modify any code (as if runtime version). The flexibility for the user is that he can "compose" his own sql-string in terms of fields, the WHERE-clause and the ORDER BY-clause, and even (in a limited way on this moment) of the tables.

由于这一切都归结为字符串操作,因此可以根据用户的意愿构建更多的灵活性。

As this all comes down to string-manipulation, much more flexibility can be built in depending on the user's wishes.

也许是一个想法。

Imb。


这篇关于在运行时版本(accde)中操作报表定义的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

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