James, If you use a Object, and want to see it everywhere, you will use the public/static not ? I have set is as Static : See my first coding for a solution with having many var in a hash or object. What should I change ? I'm not sure the "set ...
... of Static, Local and Public. Static (mostly because I see them on sample source code in the forum (Seems to be correct) Public because I need them everywhere (It seems to be correct) Local when needed I think... )) BUT... I see a lot of warnings when I compile with the build from the samples dir ...
... should be declared as LOCAL. Note that you can still pass oCustomers to a function if you wish. Why not public? Then the oCustomers is visible everywhere and we don't have to paste them by a function. One reason is that using a public violates the object rule of encapsulation. You can open ...
... lShared:= .T. super:new(,"Customers",,lShared) // database filename only exists here. ::use()Return Self So now everywhere you need to use the customers database, you just do: oCustomers:= TCustomers:New() Simple! That alone will probably eliminate hundreds of ...
... of the most fundamental tools available for your smartphones, tablets, and computers. All web links are managed centrally and are available to you everywhere. Nautical chart is the key to your travels on worldwide web. The links are organized by category. A tooltip with info text can be added to ...
Eduardo, I can only say that I tried all the available report designers. There are problems everywhere. But with EasyReport we have the complete source code. With EasyReport I have the right solution for my reports. The VRD files are INI files and can also be changed ...
... (both new and old versions) and also xHarbour. You need to change all aData := oRs:GetRows() as aData := RsGetRows( oRs ) EVERYWHERE in your application. There is no escape from this, because of the change in Harbour libraries. Depending on your requirements, you can also ...
... with action ? With a background-color it doesn't look very nice. I'm using it for a color-selection. in METHOD CreateButton() CLASS TGet I noticed everywhere < ::nHeight - 4 > http://www.pflegeplus.com/IMAGES/Getact1.jpg I tested oCGet[2]:lAdjustBtn := .T. but no difference ...
I changed the Buttonb.prg class and not to change the bitmaps everywhere I did a translation of "bitmap name for symbol code" Install the UI-Character to see the font symbols. Works only on windows 10 https://www.microsoft.com/en-us/p/ui-character-map/9nblggh5kll7 ...
... in one, I had to modify the other 4 also, or have a calculation error. After working through this, I now have 1 totals method that applies everywhere, and a change in it will always work wherever it is applied. Also, one word of caution: We often use :: to reference the object but this ...
... to print an invoice, counter sale, or estimate. The only difference is in a few titles that are printed, and the customer info This routine works EVERYWHERE except with one client where it used to work. The client installed a new printer. The customer can print invoices or estimates and it works ...
... of them have very big players backing them. JavaScript is paradigmatic in this: being a (basically) poor and reduced language, its ability to run everywhere and widely supported has made it one of the strongest competitors. On top of it there are lotsof better languages like Typescript, and, under ...
... To use all your old code you are going to have to add a lot of code to make it multiuser and you are going to have to add it (and troubleshoot it) everywhere you add, delete, or update records. And wherever you open tables. Using and tracking aliases is a nightmare which only gets worse as your ...