My Woes worsen....

[robert]

Jeff,

3) In a previous message you wrote that you had a problem with BUILDREPO.EXE. Are you using the system repository that came with the product or did you create your own system repository (because that is what the BuildRepo tool is needed for)? If you are using your own system repository, then please switch back to the normal system repository. If you don't know what I am talking about then please don't run BuildRepo.exe in the future.

As I say Robert, I'm not THAT stupid. I have 2 repositories - "Default" and "Lightning PC" it doesn't matter, the BuildRepo.exe won't run.

I never said that you were stupid. But from your answer I do see that you are not aware of the difference between the System Repository and Project repositories.

You are referring to Project repositories. The System Repository is in the CAVO28System folder. This repo contains the common code shared by all Project repositories, such as the list of functions, types and methods in the various system libraries.
The project repositories are in other folders. For example the Default project repository is in the Cavo28Data folder. If you compare the folders you will see that the System Repository has .VOA files for System1 .. System 14 as well as IDX and CDP files for these. The project repositories have no VOA files for the System libraries, only CDP files.

The BuildRepo tool is used to create a new SYSTEM repo. "Normal" users almost never use it. And to run this tool you need to copy the files from the CAVO28Unsupported folder into your Cavo28 folder.

So I still don't understand why you were trying to run the BuildRepo tool. Were you trying to reindex a project ?
In that case you need the Reindex.exe tool.

Robert

[BiggyRat]

Hi Robert, I reindex the project several times daily due to the cavopp.dll crash on compiling. I was trying to rebuild the Repository at someone's suggestion here. I had hoped it would fix any corruptions in the system files.

For example, VO seems to have an even longer memory than my ex wife! I still get messages after every reinstall saying "unable to load whateverfile.dll from D:somefolder. I haven't had a 2nd hard drive as "D:" drive for 15 years at least. I have NFI where it's getting that from, but I have to manually edit these two line in CAVOWED.inf

Path=C:Cavo28BinCustCtlX.OCX <- Originally D:
FloatBar=C:Cavo28BinVO28ORUN.DLL. <- Originally D:

Also, on my Date formatting issue, This code:

self:oDBJOBDATE1:TextValue := Transform(DToC(self:server:FIELDGET(#JOBDATE)), "dd/MM/yyyy") Results the screenshot attached..... It doesn't make any sense I tells ya!

[robert]

Jeff

Code: Select all

Path=C:Cavo28BinCustCtlX.OCX <- Originally D:
FloatBar=C:Cavo28BinVO28ORUN.DLL. <- Originally D:

On a brand new install of VO you would not have these lines. So you must have copied things over from another folder after installing VO. And apparently the file you copied had a reference to D:

And in stead of

Code: Select all

self:oDBJOBDATE1:TextValue  := Transform(DToC(self:server:FIELDGET(#JOBDATE)), "dd/MM/yyyy")

Try this

Code: Select all

self:oDBJOBDATE1:TextValue  := Transform(self:server:FIELDGET(#JOBDATE), "dd/MM/yyyy")

You are first converting the date to a string (with DTOC() and then applying a date picture. That does not work.
But to really help you we need you to produce an example that shows the problem.


Robert

[robert]

Jeff,
I need to correct myself.
I see these two lines also on cavowed.inf for VO 2.8 SP4.
I think the guy that wrote the SP4 installer (it was not me, at that moment I had already left the VO/Vulcan devteam) has included a 'dirty' cavowed.inf in the installer.

I suggest you remove the whole section
[CONTROL:OLEGEN:OLECONTROL:OCX_CustCtl.OCX.1]

from the cavowed.inf file.

Robert

[BiggyRat]

Thanks Robert, but:
self:oDBJOBDATE1:TextValue := Transform(self:server:FIELDGET(#JOBDATE), "dd/MM/yyyy")
returns the exact same as before.

I have removed the [CONTROL:OLEGEN:OLECONTROL:OCX_CustCtl.OCX.1] Section in CAVOWED.INF as you suggested too btw.

[Jamal]

Your PC environment seems poisoned!
Do you have another "clean" computer you can install VO, and import your app and see what happens.