Search results for query: *

It's hard to follow what you're trying to do but I suspect that you're trying to run a multi-step series of queries in one database call. Break down the calls into multiple steps. Your temp table will remain in place until you're ready to get rid of it. When you're running some SQL that...

Or maybe Luca got their program finished. ;)

Note that it won't do the window caption - they're doing some weird stuff there. The other thing to consider is to do your customization using Extender.

Dim modernizer As AccpacContainerObject Set modernizer = New AccpacContainerObject modernizer.ModernizeVBForm Me Sometimes you have to fiddle with a control's Load65Modernization property but the above does the bulk of the work.

There is, apparently, a VB6 only version of an expression evaluator that has been discontinued but the page says that you can contact them if you need it. https://www.aivosto.com/eval.html

I do have to say that I appreciate that the OP's question asks about moving a program written on an OS released 23 years ago to an OS released 15 years ago. :)

Is the underlying field a BLOB field? If so, I think those need to be handled differently.

Are you creating a DLL or an ActiveX control? Those types of projects cannot be run by themselves. Another program is expected to load the DLL or ActiveX control and make use of it. So Delphi is saying that you can't run your project. You can, however, tell Delphi to run another executable...

This one was super easy to Google. Dim FSO As FileSystemObject Dim TS As TextStream Dim TempS As String Dim Final As String Set FSO = New FileSystemObject Set TS = FSO.OpenTextFile(YourInputFilenameHere, ForReading) Do Until TS.AtEndOfStream TempS = TS.ReadLine 'use the Replace function...

How big is big?

I'd go with the COMApi interface over the XApi interface.

PU3 has problems.

Also watch for field names that are Access keywords. Start with just a couple of fields. You're unlikely to need to update all of the fields. Alternatively, you can create a SQL pass-through query to update the table.

The Day-End Posting Journals should have everything that you need to reconstruct the GL entries. They won't be nice to report off of via SQL but you should be able to make it work. You might check your data integrity to make sure everything is good with your data.

Sometimes MS Access would have problems if the number of columns was too long or if the total data length of a row was too long. Try with just a couple of fields and see if that helps. And there is a primary key on that table. If you're not seeing it, that might be indicative of other problems.

You could probably look at the TSynEdit controls. They'll allow you to construct lists of words to highlight. Not sure how it will work with the existing RTF formatting, however.

If it is periodic then you might have a failing network card or cable. When this happens again you can try running the dbSpy utility to get more detailed errors. You can also try pinging the database server from the affected machine to see what's up. Do the workstations ever report database...

There's also: https://www.odiglobal.com/

Drawing on the screen is a very 'expensive' task for the computer to do so when you can avoid that, you should. You could call DoEvents every X number of records instead of once per cell. I'll update the status bar when I call DoEvents so that the user can see that things are progressing...

Two ways: You can create a customized version of the OE screen with a macro (or VB6) where you can implement that control. Another way is to use Orchid's Extender product to build that business logic control. If the salespeople codes are defaulted from what is in AR and shouldn't be changed...