Recently Updated Posts

Yes, that works, thanks for the advice!

Did you by any chance install it to the "program files" directory? If yes, you could try installing to another, non-system directory. For example, make a directory c:\runbasic (or d:\runbasic if you have a d: drive) and install it there.

Hi, I used to use RunBasic to write simple programs for statistics.

I have now tried to download it on another laptop, but when I click View in Browser nothing happens.

It is Windows Vista Home Premium, and I downloaded
Free RunBasic for Windows.

Could anyone help with this please?

There have been people succeeded using frames to embed an RB program in their regular HTML pages.

You should find some solutions searching for the term embed within the past 700 or 7000 days.

Hi:

Can I do an include of a run basic page on my server from a non-run basic site?

I get errors when I use:

<!-- #include virtual="http://192.168.1.5:8008/seaside/go/runbasicpersonal?app=MenuGary&1" -->

yet I can hyper link w/o problems:
<A HREF="http://192.168.1.5:8008/seaside/go/runbasicpersonal?app=MenuGary&1">Menu</A>

I realize that the address will need to be edited so that it uses a URL. I have that part figured out.

Thanks

OK ... I commented out all commands that involve CSS, and got rid of all SQLite calls, in a really cut-down bit of code. I still get the error page. It happens whenever the server is doing something meaty, and while it is doing that, a link (or button) is clicked.

For example: I set up a page (call it [mainPage]), which does a "cls", and then loads and renders a small picture file. It also has links to a different page. Navigate away from [mainPage], using 2 PCs both connected to that application, then press a button or link to return to [mainPage]. If you press both "return" buttons more or less at the same time, the /seaside/go/..." error page appears (this is using localhost).

So, it looks like the server can't cope with a request arriving when it is already busy doing something.

Thanks for the other link, Stefan (default.css not found). However, I had already read that one; unfortunately it doesn't end with a solution.

I just did another search and found the following:



When searching make sure to increase the days to at least two years, since searching within the last 7 days just gets no hits at all in most cases.

Can you comment out any command that involves CSS?

Can you uncomment them one by one and check when it gets astray?

Just to let people know, even using only sequential files, with a home-grown locking mechanism, I still get the "/seaside/go/%5Cdefault.css/" message (though not quite as often).

So, this message is not connected to SQLite; it is presumably an issue with whatever sits behind Run BASIC. Oh well, back to the drawing board.

OK, message received. I'm gathering up my strength to re-write it, using a combination of sequential and random access files. I will still try to use the "flag file" idea to prevent locks on these flat files, though - hopefully this should work.

Thanks for all the info. Deep breath, and here we go again !

Sorry, but you can't trap the locking of the DB file, this will just freeze the session.

I would create a file if a user starts your application.
This file would be checked for its existence during the start.

Pseudo code:

If flag file exists notify user of the application being used and try again in a minute.
If it doesn't exist create it and proceed with the start of the application.
After the session has ended delete the flag file.

Good idea Stefan - I'll try this over the weekend. Something along the lines of: trap the DB lock, and issue a message like "DB busy - press 'try again' or 'go back'".

By the time the user has pressed 'try again', the lock should have cleared.

Thanks for your help.

You could block DB access while another user is using your application with a flag file or similar.

Thanks Stefan and Meekat for the heads-up on this. "PRAGMA read_uncommitted=1" looks as though it should reduce the occurrence of locks in a big way - I will try it out.

I am now going to press ahead with the project, and see how it turns out. With a low number of users, and a bit of user education, hopefully this will be a workable solution. Looking forward to the day when we can use other databases as well, but even so, what a great bit of software Run BASIC is - I'm really impressed.

For some reason SQLite locking is a major problem with Run BASIC. I've run into this many times, and in some cases I was not able to solve it.

Have you tried:
#sqlHandle execute("PRAGMA read_uncommitted=1")
Some information here:
www.sqlite.org/sharedcache.html

Good luck.
Dan