访问中断？ [英] Does Access Break?

问题描述

我们公司已被另一家公司收购，我们将通过

集成流程。 第1天之一物品正在用于跟踪部门职能的部门

数据库。一名前员工构建了我们的

Access应用程序，但他现在已经不在了。在这两年里，他已经不见了，应用程序运行良好，没有任何问题。新的
收购公司的部门有一个类似的应用程序（不确定Access或

其他一些数据库格式）功能少得多，但他们想要

保留自己的，而不是使用我们的，理由是他们的IT支持他们的部门，而我们的部门不支持，因为开发人员不再使用我们的

公司，如果发生任何事情，没有人可以修复它。

（虽然MS Office Pro是公司标准，但我们公司没有人在IT

，精通VBA）。


请两（2）个问题。首先，您作为开发人员的经验

，一旦您在Access中构建了一些东西，并且已经过多年的客户测试和使用

回到

修复破坏的东西？第二，如果某事确实破裂了在

编程中，读取另一个开发人员的编程是非常困难的，以确定他做了什么以及他是如何做到的，所以问题

可由一位新的不同的开发人员/程序员诊断和修复？


Thx ...

Earl Anderson

解决方案

Earl Anderson写道：

我们的公司已被另一家公司收购，我们将通过

整合过程。 第1天之一物品正在用于跟踪部门职能的部门

数据库。一名前员工构建了我们的

Access应用程序，但他现在已经不在了。在这两年里，他已经不见了，应用程序运行良好，没有任何问题。新的
收购公司的部门有一个类似的应用程序（不确定Access或

其他一些数据库格式）功能少得多，但他们想要

保留自己的，而不是使用我们的，理由是他们的IT支持他们的部门，而我们的部门不支持，因为开发人员不再使用我们的

公司，如果发生任何事情，没有人可以修复它。

（虽然MS Office Pro是公司标准，但我们公司没有人在IT

，精通VBA）。


请两（2）个问题。首先，您作为开发人员的经验

，一旦您在Access中构建了一些东西，并且已经过多年的客户测试和使用

回到

修复破坏的东西？第二，如果某事确实破裂了在

编程中，读取另一个开发人员的编程是非常困难的，以确定他做了什么以及他是如何做到的，所以问题

可由一位新的不同的开发人员/程序员诊断和修复？


Thx ...

Earl Anderson

偶尔备份数据库。

很多事情可能*偶然*发生在;破" Access

应用程序中的代码;它部分取决于写入代码的内容以及它是如何编写的。至于修复别人的申请 - 这主要取决于

申请是否写得大大超过了想要排除故障的人的技能水平，以及如何那个人好多了？b $ b研究他/她可能不熟悉的问题。


hth

Earl Anderson ; < @ ***** @ optonline.netwrote in message

news：H7 ************** @ newsfe12.lga ...

我们公司已被另一家公司收购，我们将通过

整合流程。 第1天之一物品正在结算

departmental

用于跟踪部门功能的数据库。一名前员工建造了

我们的

访问应用程序，但他现在已经不见了。在这两年里，他已经不见了，应用程序运行良好，没有任何问题。新的

收购公司的部门有一个类似的应用程序（不确定Access

或

其他一些数据库格式）功能少得多，但是他们想要保留他们自己而不使用我们的产品，理由是他们的
支持他们的/ blockquote>

IT

部门虽然我们不是，因为开发人员不再使用我们的

公司，没有人可以修理它，如果有什么事情发生在

它。

（虽然MS Office Pro是公司标准，但我们公司没有人在

IT

，流利的VBA）。


请两（2）个问题。首先，你的体验是

开发商

一旦你在Access中构建了一些东西已被客户广泛测试和使用

多年来您被回拨

到

修复破坏的东西？第二，如果某事确实破裂了在

编程中，读取另一个开发人员的编程是非常困难的，以确定他做了什么以及他是如何做到的，所以问题

可以通过新的和不同的

开发人员/程序员来诊断和修复？

>

Thx ...

Earl Anderson

Earl Anderson写道：

我们的公司已被另一家公司收购，我们将通过

集成流程。 第1天之一物品正在用于跟踪部门职能的部门

数据库。一名前员工构建了我们的

Access应用程序，但他现在已经不在了。在这两年里，他已经不见了，应用程序运行良好，没有任何问题。新的
收购公司的部门有一个类似的应用程序（不确定Access或

其他一些数据库格式）功能少得多，但他们想要

保留自己的，而不是使用我们的，理由是他们的IT支持他们的部门，而我们的部门不支持，因为开发人员不再使用我们的

公司，如果发生任何事情，没有人可以修复它。

（虽然MS Office Pro是公司标准，但我们公司没有人在IT

，精通VBA）。


请两（2）个问题。首先，您作为开发人员的经验

，一旦您在Access中构建了一些东西，并且已经过多年的客户测试和使用

回到

修复破坏的东西？

计算机程序是逻辑指令。如果一个程序今天有效，那么明天就可以使用
。如果程序有语法错误或逻辑错误

会发生同样的错误，你不应该期待不同的结果。


但是你可以有一张网卡/电缆故障。或者计算机之间可能存在

服务补丁差异。或者可能通过卸载

某些东西，需要的参考文献被破坏。


我应该认为在2年的使用中你会发现

现在问题。


在你的情况下，你拥有的是你将拥有的。它听起来并不像你有任何需要增强或修改程序。在

的未来，您可能需要进行调整。我会考虑你将来可能需要的b $ b。


其次，如果某事确实破坏了在

编程中，读取另一个开发人员的b
节目以确定他做了什么以及他是如何做到这一点非常困难，这样一个问题

可以由一个新的不同的开发人员/程序员诊断和修复吗？

任何值得他的盐程序员都可以阅读程序员代码和

增强或修改它。现在为什么程序员做了一些事情是另一个问题。假设代码是

如果Status =" A"然后

扩展=成本*数量

否则

扩展=成本* 2

Endif

好​​的，所以如果状态是A然后乘以成本时间数量，否则

将成本乘以2.为什么？在这种情况下，你需要问一个

用户为什么会这样。希望周围有一个用户

了解其背后的原因如果程序员没有记录

它。并非所有代码都记录在这个世界上。


在您的情况下，您的公司被另一个人收购。并且它们的IT部门支持
。在这件事情上，你可能正在敲打一块砖墙，并且可能会更好地咧嘴笑着承受它并且可以更好地回到过去的岁月但仍然坚持到现在。

Thx ...

Earl Anderson

Our company has been acquired by another company and we are going thru the
integration process. One of the "Day 1" items is settling on a departmental
database used to track departmental functions. A former employee built our
Access application, however he is now long gone. During the 2 years he''s
been gone, the application has worked just fine with no problems. The new
acquiring company''s department has a like application (not sure if Access or
some other db format) with much less functionality, however they want to
keep their own and not use ours, citing that theirs is supported by their IT
Department while ours is not and since the developer is no longer with our
company, there is no one who could repair it should something happen to it.
(Although MS Office Pro is a company standard, our company has no one in IT
that is fluent in VBA).

Two (2) questions please. First, has it been your experience as developers
that once you build something in Access and it has been tested and used
extensively by the client over a period of years that you are called back to
fix something that "broke"? Second, if something did "break" in the
programming, is it extremely difficult to read another developer''s
programming to determine what he did and how he did it, so that a problem
could be diagnosed and repaired by a new and different developer/programmer?

Thx...
Earl Anderson

解决方案

Earl Anderson wrote:

Our company has been acquired by another company and we are going thru the
integration process. One of the "Day 1" items is settling on a departmental
database used to track departmental functions. A former employee built our
Access application, however he is now long gone. During the 2 years he''s
been gone, the application has worked just fine with no problems. The new
acquiring company''s department has a like application (not sure if Access or
some other db format) with much less functionality, however they want to
keep their own and not use ours, citing that theirs is supported by their IT
Department while ours is not and since the developer is no longer with our
company, there is no one who could repair it should something happen to it.
(Although MS Office Pro is a company standard, our company has no one in IT
that is fluent in VBA).

Two (2) questions please. First, has it been your experience as developers
that once you build something in Access and it has been tested and used
extensively by the client over a period of years that you are called back to
fix something that "broke"? Second, if something did "break" in the
programming, is it extremely difficult to read another developer''s
programming to determine what he did and how he did it, so that a problem
could be diagnosed and repaired by a new and different developer/programmer?

Thx...
Earl Anderson

Back up the database once in a while.

a lot of things could *potentially* happen to "break" the code in an Access
application; it depends in part on what''s written into the code and how it''s
written. as for fixing somebody else''s application - that mainly depends on
whether the application was written substantially above the skill level of
the person trying to troubleshoot it, and how good that person is in
researching problems that s/he may not be familiar with.

hth
"Earl Anderson" <is*****@optonline.netwrote in message
news:H7**************@newsfe12.lga...

Our company has been acquired by another company and we are going thru the
integration process. One of the "Day 1" items is settling on a

departmental

database used to track departmental functions. A former employee built

our

Access application, however he is now long gone. During the 2 years he''s
been gone, the application has worked just fine with no problems. The new
acquiring company''s department has a like application (not sure if Access

or

some other db format) with much less functionality, however they want to
keep their own and not use ours, citing that theirs is supported by their

IT

Department while ours is not and since the developer is no longer with our
company, there is no one who could repair it should something happen to

it.

(Although MS Office Pro is a company standard, our company has no one in

IT

that is fluent in VBA).

Two (2) questions please. First, has it been your experience as

developers

that once you build something in Access and it has been tested and used
extensively by the client over a period of years that you are called back

to

fix something that "broke"? Second, if something did "break" in the
programming, is it extremely difficult to read another developer''s
programming to determine what he did and how he did it, so that a problem
could be diagnosed and repaired by a new and different

developer/programmer?

>
Thx...
Earl Anderson

Earl Anderson wrote:

Our company has been acquired by another company and we are going thru the
integration process. One of the "Day 1" items is settling on a departmental
database used to track departmental functions. A former employee built our
Access application, however he is now long gone. During the 2 years he''s
been gone, the application has worked just fine with no problems. The new
acquiring company''s department has a like application (not sure if Access or
some other db format) with much less functionality, however they want to
keep their own and not use ours, citing that theirs is supported by their IT
Department while ours is not and since the developer is no longer with our
company, there is no one who could repair it should something happen to it.
(Although MS Office Pro is a company standard, our company has no one in IT
that is fluent in VBA).

Two (2) questions please. First, has it been your experience as developers
that once you build something in Access and it has been tested and used
extensively by the client over a period of years that you are called back to
fix something that "broke"?

Computer programs are logic instructions. If a program works today it
should work tomorrow. If the program has syntax errors or logic errors
the same error will occur and you should not expect different results.

But you could have a network card/cable malfunction. Or perhaps a
service patch difference between computers. Or perhaps by uninstalling
something a reference that is needed is broken.

I should think that in 2 years of use that you would have discovered
problems by now.

In your case, what you have is what you will have. It doesn''t sound
like you have had any need to enhance or modify the program. In the
future, you may need to make adjustments. I would consider what you
might need in the future.

Second, if something did "break" in the

programming, is it extremely difficult to read another developer''s
programming to determine what he did and how he did it, so that a problem
could be diagnosed and repaired by a new and different developer/programmer?

Any Access programmer worth his salt could read the programmers code and
enhance or modify it. Now why a programmer did something is another
matter. Let''s say the code is
If Status = "A" then
Extended = Cost * Qty
Else
Extended = Cost * 2
Endif
OK, so if the status is A then multiply the cost times qty otherwise
multipley the cost by 2. Why is that? In this case you''d need to ask a
user why this occurs. Hopefully there is a user around that
understands the reasoning behind it if the programmer did not document
it. Not all code is documented in this world.

In your situation your company was aquired by another. And it is
supported by their IT department. You might be banging against a brick
wall on this matter and may be better off grinning and bearing it and
yearning back to the days of old but stuck in the present.

Thx...
Earl Anderson

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