Replies

Hi Rory,

No, the brackets dont appear to make a difference. I could use the abs() you suggested, but the column is the leading column on an index in a large table, and putting a function on the column will force a table scan.

I am certain this issue pertains to using an ODBC driver with OLE DB – and for some reason it is being split. It is certainly more bizarre, that if I use the connection via a DSN it works! It has to be something that is happening with the DSN less connection.

Hi All,

I get a problem when I run a select statement against a sybase database from VB/ASP. The problem appears when the select contains an or, ie. “select deal_nr from fxcash where deal_nr = 10090 or deal_nr = -10090”

If I dont include the or, the code works fine. If I include the or, i get the following error:

Microsoft OLE DB Provider for ODBC Drivers error ‘80040e21’
Microsoft OLE DB Provider operation generated errors. Check OLE DB status value, if available. No work was done.

I checked the knowledge base and it says this can happen when OLEDB_SERVICES flag is missing from the registry, but this is there on my machine.

Again, if I remove the or, the code works fine. It appears that ADO is splitting the statement into two parts. Also, I should have mentioned – I create the ado connection DSN less. If i specify a DSN this works!

Does anyone have any ideas?

Thanks for your help.

Regards

Al

Hi HansV,

Thanks for the quick reply, but unfortunately it makes no difference.

Regards

Al

If you want a book, Dan Applemens “Visual Basic Programmers Guide to the Win32 API” is very good. Other than that there are probably a few good websites around.

If you throw a do events in to the loop, you should be ok.

Al

Tim,

I just checked the command line options (vb6 /?) and what you want is

vb6 /make projectname

This tells VB to compile projectname and make an executable from it, using the existnig settings stored in the project file.

HTH

Al

Using shell in the command line is the best way to compile your apps. Why not shell the command and dont show the window (if it is the dos window puts you off). Shell the command prompt hidden

iReturn = Shell(sCommand, vbHide)

then get a Handle to the process
hProc = OpenProcess(PROCESS_ALL_ACCESS, false, iReturn)

then in a loop
check GetExitCodeProcess hProc, iExit
and exit when iExit = &H103

I can’t remember the comment to compile – but it is in MSDN.

Cheerz

Al

Um, When you have a DSN, which ODBC enabled applications use to connect to data sources, and an application, which uses these DSN’s, hardcodes a link to a file path – rather than checking from the DSN – that IS a bug.

If it looks like a duck…

Regards

Al