xsharp.eu

Well, thanks to Robert, my errors are way down on compilation (it still happens when I do a "Touch All Entities" however) but at least it doesn't do it all the time anymore.... BUT...

My original problem remains. Even with SetCentury in the correct order as Jamal pointed out, it's still wrong IN THAT ONE SCREEN...

Jeff,

BiggyRat wrote:Well, thanks to Robert, my errors are way down on compilation (it still happens when I do a "Touch All Entities" however) but at least it doesn't do it all the time anymore.... BUT...
My original problem remains. Even with SetCentury in the correct order as Jamal pointed out, it's still wrong IN THAT ONE SCREEN...

A shot in the dark.

Do you have one DateSetting call in your start function/method or are you setting it all over?

Hi Johan, here is my start method:
method Start() class App
local oMainWindow as TopAppWindow
Local cWorkDir as String
cWorkDir := WorkDir()
request dbfcdx
self:Initialize()
SetDateFormat("dd/MM/yyyy")
SetInternational(#Clipper)
SetCentury(true)
oMainWindow := TopAppWindow{self}
oMainWindow:Show(SHOWZOOMED)
oMainWindow:Caption := cAppVersion
RddSetDefault("DBFCDX")
SetExclusive(FALSE)
SetDeleted(true)
oMainWindow:Icon := BM{}
oMainWindow:IconSm := BM{}
SetEpoch(2000)
SetAmPm(true)
Set Decimals to 2
self:SetGlobalValues()
Run("FixOutlook2016.reg")
oMainWindow:EnableSystemMenu(FALSE)

oMainWindow:ShowMainMenu()
self:Exec()

Return self


However, I have been throwing others in the code around that particular screen to try and force the issue...

Jeff

BiggyRat wrote:Hi Johan, here is my start method:

Code: Select all

        SetDateFormat("dd/MM/yyyy")    
        SetInternational(#Clipper) 
        SetCentury(true) 
        RddSetDefault("DBFCDX")
        SetExclusive(FALSE)
        SetDeleted(true) 

However, I have been throwing others in the code around that particular screen to try and force the issue...

I realise you added code, I just get the impression there is maybe another "Set" somewhere that is messing it up in the chain to that Window... Here is my default start code Settings:

Jeff,
Make a new mef, make a new Form, put your Browser on it- works yes or no?
If yes, copy the specific code in, finally delete the faulty mef and go on
If no, start above with new app.
If still no, create a new repo.

Karl, it;'s a 100% new installation, so it's very unlikely to be a corrupt Repo, but I can't rebuild the Repo in any event, as I get the attached error...

Jeff,
first things first: did you try a new mef?
What happens,when you remove the picture clause?
Finally, I didn't write "rebuild" the repo, but: make a new one. If that is also not possible, I'm off my limits, then you need the "pros". If this works, create a new app, import the functioning mefs one by one, then copy the code from the faulty one into an empty one.

That said,I'm very suspicious of your system at all

Replying on #9376:

Hello Jeff,


You must be missing something in the cavo installation. I only know a side by side error from my X# DLL which I run from VO. In order to avoid the need to register it (regasm.exe) for all users, I created a manifest in VO. This all has to carefully match the DLL being called otherwise my exe won't start.

Now there are 3 options:

1 A complete new setup, then import your AEF's. Allow new ones to be created if absent because they will be overwritten later in the import automatically. Quit VO and restart (to avoid resource errors which appeared in later W10 versions) Then (and not earlier) use VOPP to build all (because it know how the order to compile depending aef's). You should be ok afterwards and this is the least amount of work

2 Check the W10 application log which will give you info about the Side by Side error.

3 To know exactly what happens, use the below procedure. This may help you find what's missing.

Dick

Procedure SXTrace

The program should be at location:  C:WindowsSystem32sxstrace.exe
Administrative privileges are required to use sxstrace.exe

1 Open Command Prompt (Admin)
2 Start SXTrace by running the  command:  sxstrace.exe Trace -logfile:tracetest.log
Note: Make sure you run the command on a directory with write permissions. As an alternative, point the –logfile parameter to a directory with write permissions  
3 Run the program causing the error message (from Explorer or another prompt). When the error message appears click OK
4: Stop Trace (by pressing Enter in the DOS box)
5 :Convert log to readable format. The tracetest.log from above is a binary formatted file. This command will convert into human readable format by parsing the binary log file and creating a text file
sxstrace.exe Parse -logfile:tracetest.log -outfile:tracetest.txt

Sample:

C:WindowsSystem32sxstrace.exe Trace -logfile:c:temptracetest.log
C:WindowsSystem32sxstrace.exe Parse -logfile:c:temptracetest.log -outfile:c:temptracetest.txt

Oh I've created a new repository several times. That didn't make any difference. Why are you suspicious of my system? The whole PC is only 6 months old. Probably a stupid question, but could my system be too fast for the compiler? It's not that special, but it's ddr4 RAM, 2tb SSD, I7 etc...

Well,you shouldn't see any of these problems with rebuild. If there were a general problem with w10 or newer pcs, there would have been a ton of complaints on the ng...