Windows 64-bits

[driessen]

Hello,

How about FWH - xHarbour applications on Windows 64-bits ? Are there any know problems ?

I experienced a problem.

I use this code to open files :

Code: Select all  Expand view

STATIC FUNCTION NetUseJuda(cFileName,lExclusief,nWaitSeconds,cAlias,cTaal,cOH)

   LOCAL lForever
   LOCAL lRedo     :=.T.
   LOCAL nWait

   DEFAULT(nWaitSeconds,0.1)
   DEFAULT(cTAAL,"N")
   DEFAULT(cOH,0)

   lForever=(nWaitSeconds==0)

   DO WHILE lRedo
      nWait := nWaitSeconds*2
      DO WHILE lForever .OR. nWait>0
         IF cAlias = NIL
            IF lExclusief
               USE (cFileName) EXCLUSIVE NEW
            ELSE
               USE (cFileName) SHARED NEW
            ENDIF
         ELSE
            IF lExclusief
               USE (cFileName) EXCLUSIVE ALIAS (cAlias) NEW
            ELSE
               USE (cFileName) SHARED ALIAS (cAlias) NEW
            ENDIF
         ENDIF

         IF !NETERR() .AND. USED()
            RETURN .T.
         ENDIF
         INKEY(.5)

         nWait--
      ENDDO
      IF cOH <> 1
         MsgAlert("The file "+cFileName+" cannot be opened !!!","Be careful")
      ENDIF

      lRedo := .F.
   ENDDO

   USE

RETURN .F.

In Windows 32-bits, there is no problem at all. In Windows 64-bit (in my case Windows 7) though I sometimes get the alert that the file cannot be opened.

Does anyone have any idea why this problem occurs ?

Thanks a lot in advance.

[James Bott]

Michel,

Are you sure you are not trying to open it exclusive when it is already opened? Or, tying to open it shared when it is already opened exclusive would give you the message.

Or, you could be using an alias that is already in use.

Maybe a rights issue?

Of course, none of these has anything to do with 64bits.

Regards,
James

[driessen]

James,

I'm sure that the files are not opened by someone else. Also the rights on the harddisk are OK.

The PC on which the problem is happening, is a standalone PC which is not connected in a network.

I never had this problem on a Windows 32-bits PC.

So, I don't know why this problem suddenly occurs on a Windows 64-bits PC.

But thanks for your attention.

[James Bott]

Michel,

Maybe it would help if you put in a msgInfo(neterr()) so you can see what the error is. As your code is now, all neterr()s just show that the file can't be opened, but not why.

Regards,
James

[Richard Chidiak]

Michel

I am running my app under windows seven 64 bits, i have no problems with it

HTH

Richard

[driessen]

James,

To my opinion NetErr() only return .T. or .F., doesn't it ?

Thanks.

[driessen]

Hello,

I have changed the properties of the shortcuts and I changed the compatible mode to "Windows XP (Servicepack 3)".

I noticed that the error occurred a lot less. It is a lot better now.

Just to share my experiences.

Thanks

[James Bott]

Michel,

>To my opinion NetErr() only return .T. or .F., doesn't it ?

Yes, you are correct. I must have been thinking of ferror().

James