crash and burn #2

it happened again today.

servoy exited without warning of any kind, and now
the solution file cannot be opened (servoy just hangs,
then exits when I try to open the file)

everything I did today is lost. the person I report
to is furious, and considering termination of the
project.

the only clue I can offer is that I was working
with a calculated field, adding code to the calculation,
and trying it out.

are there limitations on what can be done in
a calculated field?

answers to your previous questions:

which version do you use of servoy?
r2 2.0 beta6-build 260

do you have any errors in youre .log.txt file?
I don’t know of any such file. I just searched the
hard drive, and no file by that name exists.

Can you export the solution?
yes. but importing it back into servoy just
results in the same unusable solution file.

is there anything you can do to repair the solution export
file if I send it to you? I’m trying very hard to get
a pilot project up and running by next weekend, and
I’m loosing ground rapidly.

any help would be greatly appreciated.

do you have any errors in youre .log.txt file?
I don’t know of any such file. I just searched the
hard drive, and no file by that name exists.

Should be in …/Servoy (your main Servoy folder)

Can you mail me your export file?
I’ll see what we can do.

Thanks.

maarten:

do you have any errors in youre .log.txt file?
I don’t know of any such file. I just searched the
hard drive, and no file by that name exists.

Should be in …/Servoy (your main Servoy folder)

Can you mail me your export file?
I’ll see what we can do.

Thanks.

there’s no such file on my machine.

I’d be happy to mail the export file; where would
you like it sent?

You can use the email button at the bottom of my post(s).

are you sure it isn’t there?
it starts with a dot so on the mac it is marked as hidden

We’ve found some reserved words in the solution file.

Problem is that reserved words differ form database to database. A reserved word in eg. MySQL could be perfectly acceptable in Firebird etc..

Therefore, we’ve gathered a list of reserved words of most databases that will be rejected by Servoy , IF you create them from within Servoy.

So it’s always safer to create your columns in Servoy.

For those who are using a database tool for creating colums, we’ll extend the manual with a list of all reserved words.
(attached is a textfile (.txt) with res. words)

It seems I’ve got the same problem. I exported my solution, deleted the solution from repository and now can’t import back; Servoy reports a reserved word used as column name (“password”).

I really need help here.

Ronnie

wait one day for RC11.. then we have an option in the importer so that you can ignore those words (won’t be checked on so if the current database finds it ok then you are lucky)