Very Computer

1. Sybase SQL Anywhere and MS VB 4.0 32-bit DLLs

I wrote a collection of procedures in VB 3.0 last year, which work
nicely under VB 3.0.  However, after converting them to VB 4.0 32-bit
version, I'm running into trouble.

I'm aware of case-sensitive function and library naming in VB 4.0
32-bit, but I can't seem to use even the most basic function as in the
past.

Here is some sample code:

'' Declaration in standard module

Declare Function WSQLEXEC Lib "I:\SQLANY50\WIN\WSQLCALL.DLL" Alias
"WSQLexec" (ByVal cmd As String) As Long

" Calling Subroutine

Sub WSQLexec_(ByVal pSQL As String, ByVal pCaller As Variant, ByVal
pDEBUG As Integer)
''
'' Wrapper for WATCOM HLI function of same name.
''

Dim nErrorCode As Long
ReDim bytSQL(0 To Len(pSQL)) As Byte

bytSQL = StrConv(pSQL, vbFromUnicode)
nErrorCode = WSQLEXEC(bytSQL)
HaltHLIerror nErrorCode, pSQL, pCaller + "WSQLexec()", pDEBUG

End Sub

The error "can't load DLL" appears when WSQLEXEC(bytSQL) is called.
The DLL is definitely available, but I can't get this to work.

Any help would be appreciated.

------------------------------------------------------*

-
- Coral Springs, FL, USA
-----------------------------------*

2. Help with DDE

3. Migrating 16-bit ODBC DLL (SQLServer) to 32-bit ODBC DLL (MS Access)

4. Parameter Stored Procedure in A2K

5. Creating 32 bit .DLL for VFP 3.0

6. Slow start on WindowsXP

7. Odbc.dll declarations in VB 4.0 (16-bit)

8. VIRTTIMER and TIMESLICE

9. Calling 16 bit Dll from 32 bit program

10. thunking (calling 16 bit dll's from 32 bit app)

11. How can I access 32 bit access with 16 Bit Visual Basic ( VB 3.0 or VB 4.0 16 bit)

12. Migrating from 16-bit btrieve dll to 32-bit