Search results
Search results 21-40 of 40.
Dear visitor, welcome to Jabaco - Community.
If this is your first visit here, please read the Help. It explains in detail how this page works.
To use all features of this page, you should consider registering.
Please use the registration form, to register here or read more information about the registration process.
If you are already registered, please login here.
Ok, so in the end, it sounds like I was more or less right: If you want to "upgrade" the VB and VBA compatibility functions in your Jabaco installation, you just: 1) Download the latest jabaco.jar you can find, from links above or the "framework" downloads. 2) Close Jabaco if you are using it 3) Rename your old jabaco.jar, and replace it with the new one 4) Restart jabaco and you are set to go for both using new functions, as well as compiling. It is mentioned above however that things like the ...
Hmmm, the compiler may be highlighting the wrong item as the problem point. As for the last two lines doing the same thing in VB, I agree, though you may need to use the "set" command such as: set picture1.picture=LoadPicture("something.jpg") That being said, including the set command in Jabaco did not help. The PaintPicture method expects an "image" type as an argument. The LoadPicture function returns an "image" type, so all is well. My guess is that the "Picture" property of the Picturebox co...
What you say makes sense, and your work around is easy. As a compatibility issue for importing VB6 code, VB does treat the variable name as a read-only property, and many vb programmers have used it (myself included) for odd things in applications. If name could be presented in Jabaco the same way, it would make for easier project imports, but definitely not a major issue.
Oh, not surprising that Format isn't implemented in Jabaco, in VB it does nearly everything. See if this works: text1.text=Year(Now) & "-" & Month(Now) & "-" & Day(Now) That's not the best, I know, you'll lose leading zeros. But I just tried this, and it didn't work, returned very odd values. Obviously we need to remember that Jabaco is a work in progress, and not necessarily intended as an exact replacement of VB. Still, starting to be clear to me that date functions in general need a lot of wo...
Hi, I had no idea that would work in VB6, I had to try it. Perhaps this was included in vb for backward compatibility/etc. The proper statement should really be: Text1.text = Now Which Jabaco should support.
In addition to the main download, I see the "Framework" downloads, a list of dated versions of the Jabaco.jar file. This is probably pretty obvious, but with my zero java knowledge, I wanted to verify: I assume these downloads are here so you can update your jabaco installation to include all the latest bug fixes, enhancements, etc. Is it true that all you do is download the framework file you want, rename it to jabaco.jar, and overwrite your old one? Does the change immediately take effect in t...
When you create a form, you can give it a name in the form properties. However in code, the "name" property is not available as expected. So including something like "If MyForm.Name = something then" does not compile. Quick test is to open new SDI application, add command button and include this line of code in click event: Msgbox Form1.Name
For fun I started implementing a quick solution for finding a form by name and giving it focus. I noticed this potential oversite in Jabaco: When you create a form, you can give it a name in the form properties. However in code, the "name" property is not available as expected. So including something like "If MyForm.Name = something then" does not compile. I will also post this issue in the "bugs" section.
More Information: I've confirmed that this is a problem with the ctrl-B shortcut for creating a breakpoint. If I create a breakpoint by clicking in the left margin, the red marker appears and the breakpoint works. If I create a breakpoint by pressing ctrl-B while the cursor is on the line, the red marker appears exactly like above, however the breakpoint is ignored.
I placed breakpoints in a button click event using ctrl-b, the red dots showed up in the left margin. But when I ran the project using F5, the blew right by the break points and executed everything. Do the breakpoints work for others?
Well, for questions like "what would vb6 do?" I finally feel qualified to answer! If it is a nonsense string value, it will cause a "type mismatch" error. Same is true of an empty string. A null value passed in causes "invalid use of null" error. A numeric value passed in (like integer or long) will actually be converted to a date, but as the internal storage of java dates vs vb dates may differ, this last one should probably not be supported, would prefer a "type mismatch" myself.
Good to know people are still involved, this is a fun tool to play with. I'm a little confused in general about some other compatibility issues--since there was no IsDate function that I could see, I thought I'd write my own by simply doing the following: Function MyIsDate(sData as String) as Boolean Dim dTemp as Date On Error Goto NotADate dTemp=CDate(sData) MyIsDate=True Exit Function NotADate: MyIsDate=False End Function However, this totally did not do what I expected. I expected that if I h...
Well, thank you for your efforts in any case. Maybe a future JRE update will fix the problem. Searches on google indicated that perhaps swing was updated, and did not maintain backward compatibility... the good news is that aside from the annoying pop-up, I can still run projects.
More Info: If I create a SDI project with just form and a label, the pop-up error occurs. If I create a console application with a single added line of code MsgBox "Hello!", the application runs with no error pop-up.
Ok, here we go. Originally, projects worked fine on jabaco installation. After automatic upgrade to 6.23, the startup error appeared, but projects still execute after hitting "continue." When compiled as either an .exe or .jar, the error still pops up, on both the original machine, and also on another that has no jabaco installed, only JRE v23. Both machines are XP SP3 with really no differences, English (US) with whatever character set would be standard (not familiar with that...) I looked thro...
XP SP3. I'll see what I can do with the new framework file, not sure what I'm supposed to do with it, replace my existing one I assume...
In my install directory, Jabaco.jar is dated 8/8/2009 1:01 PM.
Is there a master document that indicates which subroutines and functions from VB and VBA have been implemented in Jabaco? I don't see any docs here or in my installation. I tried a few functions at random and figured out that it appears things are missing--an example would be date functions like IsDate, DateDiff, etc... Anyone have a quick reference that simply lists which funcitons I can expect to use in Jabaco? Thanks
More Info! I can confirm that this problem is because of the recent java upgrade to v23. As I mentioned before, the test app ran perfectly on the machine I installed Jabaco on. That machine did not have Java on it, so the Jabaco installer installed it for me. It installed an older version (possibly v16?) apparently. I didn't notice this, but today Java automatically prompted me to install the latest v23 version. So I did. Since then, this machine exhibits the exact same startup problem as my oth...
I'm another newbie in the same boat--installed Jabaco, then created a hello world app. The app ran normally on the machine that I installed Jabaco on. So I decided to compile it as a .jar and try it on another machine. Since the other machine had no java components on it whatsoever, I installed JRE v23. Then I tried running the .jar. As mentioned above, the NoSuchMethodError is immediately displayed, but if I hit ignore, the hello world app functioned normally. The posting above indicates instal...
Bugreports and known bugs » 
[VERSION 1.5.2] Form Name Property not available at runtime