Home > Software engineering >  VB development of the software flash back
VB development of the software flash back

Time:11-08

Before the former colleagues to develop VB software, used for many years, under the environment of winxp and Windows 7 can be stable operation, the latest to open, flash back page, the software itself should be no problem, don't know if the environment changes (because IT unified management background, there may be patched or action, such as office to upgrade, and)

The problem is that don't have the source code, also contact less than the original author,

Everyone a great god, is there any way to get more information or suspected direction?

CodePudding user response:

What type of software?

CodePudding user response:

Monitoring the production data of software, is bad, but there are drawing, there are calls to office components,

reference 1st floor milaoshu1020 response:
what type of software?

CodePudding user response:

If there are errors, or have the log is better positioning error;
It's hard to;
You can try to other computers, see can normal operation;

CodePudding user response:

Yes, now is wrong and log all have no,

As long as you don't quit restart computer software is in use, as long as the exit again into flash back,
Only a colleague didn't restart the software also suddenly can't use, but open the office tools, the software often ran out of flash, process has always been there,

Software is opened even internal public scrutiny to see if the new version is more, all flash back are now at the beginning of the checking, the problem is and public disk is the same software version,

The
reference 3 floor milaoshu1020 response:
if there are errors, or have the log is better positioning error;
It's hard to;
You can try to other computers, see can normal operation;

CodePudding user response:

Big probability is reading upgrade information failed, didn't do error handling,

CodePudding user response:

Read less than previous upgrade information, the software will keep the local version, don't do update,

reference 5 floor vansoft reply:
big failure probability is read upgrade information, don't do error handling,

CodePudding user response:

refer to 6th floor romainroland response:
read less than the previous upgrade information, the software will keep the local version, don't do update,

Quote: refer to the fifth floor vansoft reply:

Didn't do big failure probability is read upgrade information, error handling,


There are two kinds of failure, one kind is not read, one kind is read, but the information is wrong,

CodePudding user response:

May be the result, control does not support not just on the client to install the vb system, then the source code debugging

CodePudding user response:

refer to the eighth floor zcyzzzm response:
may be the result, control does not support not just on the client to install the vb system, then the source code debugging

yes, should can't find the answer here
  • Related