Search results for query: *

Here's an article worth reading, more generally on the topic of optional conditions and how they are better optimized: https://www.sommarskog.se/dyn-search.html One shot - not the only one - is forcing recompilation, i.e. make SQL Server optimize for the current case, not the general case, which...

Hmm, it should indeed be simple boolean algebra to disregard one branch of this, seems the SQL optimizer does not realize the variable is constant during the query. In theory it could change, but there would need to be some section in the query itself, setting @Boolset. I think it could differ...

Even if you solved your problem alone, it would be worth keeping the question and posting the solution. Or just delete your thread.

...you had to release with a VFP application. I remember that was causing some effects on reports, generally printing a few % wider and causing ***** in numeric report controls that were precisely dimensioned in previous versions. If I'm wrong about GIF animation support in VFP7 the animation...

Well, putting an image control on a form and setting the Picture interactively (double click the picture property and pick the MORPHFOX.GIF from the file open dialog) it even animates in design mode immediately. I don't see it depend on how you set the picture.

I know VFP9 introduced PNG rendering and SP1 or 2 fixed a bg with PNG transparency. That has nothing to do with GIF, but pretty sure VFP9s integration with GDI+ is best in the last version of it, if you use previous VFP versions, that might be the root cause of the GIF not working. If you could...

Can you post your gif? In VFP9 this should show the FoxPro logo morphing from new to old logo and back: _screen.AddObject("image1","image") _screen.image1.Picture=Home()+"GRAPHICS\GIFS\MORPHFOX.GIF" _screen.image1.Visible = .t. This doesn't require any code to start animating, just setting the...

You don't do use the PROMPT clause, which would allow choosing pages to print. Nor do you use a FOR clause, which would limit what records to print. I don't see how you would get the behavior you describe. So I think I'd still need to see more details about what this is about.

I wish you good luck with that. Windows 10 is phasing out of support in October this year, and I think this is not even the major problem you'll face. Do you have the prg or only the fxp file? (I assume FCO is a double typo on c for x and o for p - you can edit your posts, by the way, to...

You don't do use the PROMPT clause, which would allow choosing pages to print. Nor do you use a FOR clause, which would limit what records to print. I don't see how you would get the behavior you describe. So I think I'd still need to see more details about what this is about.

I have posted a solution. I n fact the only solution that would work by your conditions to not virtualize. I mean, when you don't realize DOSBOX-X is a vitrtualization solution, you have not understood the sentence If I would overlook your condition, there's one more very frequently used other...

Makes me wonder why would anyone still use tinytext, which is limited to 256 bytes, so it's just like varchar(256) and it will turn to memo, because 256>254, as simple as that. And once you look up what tinytext in a MySQL or MariaDB can store, you know how it doesn't compare to simple...

You are now using a virtual environment, just saying. There's nothing wrong with that.

Autoexec.bat would define what starts automatically, not autoexe, nor autoexec alone. And it has to be in the start drive, that's still the same when it comes to a DOS emulator like DOSBOX-X, doesn't it? Well, and otherwise you get to the command prompt. You're as free to start what you want to...

Still not clear what you had. If it was varchar(20) and varchar(50) you have to do CursorSetProp("MapVarchar",.T.,0) and you should also have CursorSetProp("MapBinary",.T.,0). Before doing any query, once at the start of a datasession. Anyway, memo does no harm, you can bind both a textbox and...

Reference? If you have one, I think they first must have installed DOS itself. Windows isn't DOS based since Win98 and so that's about 30 years. DOS simply is a separate Installation and you'll need an original MS DOS. And then compatibility isn't an issue, you install FP DOS or an FP DOS...

In general to have control about the result field types on the VFP side it's most elegant to use remote views or cursoradapter instead of SQLEXEC. Anyway, if your MariaDB column is shorter than 255 it will arrive as char or varchar in VFP with no need to CAST, if you need to CAST to get a...

Maximum for a VFP DFB char field is 254 characters, so anything longer is turned into a memo. So if your MariaDB is overdimensioned in these fields, shorten them. If that's okay with the data, the memo field type is what you'll need and want and there's nothing wrong about that.

Could you post your REPORT FORM commands, whether you use VFP9, and if so whether you print with reportbehavior 80 or 90. You might be using the 90 mode with the reportpreview.app/reportoutput.app in the IDE - running source code, and missing to provide them with the exe, so it falls back to...

Even VBA has StrReverse(), so whatever word list you have, reversing that is simple and fast, T-SQL also has a function you could use after importing the word list: https://learn.microsoft.com/en-us/sql/t-sql/functions/reverse-transact-sql?view=sql-server-ver16