Downloading that manual.
Would it be possible/practical for versions of documentation to be on the
web site, so that when there’s a rev, it’s clear (or do you announce?).
I notice the download has a very specific rev on it.
Thanks for all your work, and to everyone who helped on this thread.
Anne
Online help, documentation that can be downloaded from the Servoy
Developer/Documentation web page link, and the printed books are
updated when there is a whole number or “dot” number Servoy release.
For example, the documentation updates were made available for
the final release of Servoy 1.1 and Servoy 2.0, but will not be changed for
online Help (F1), on the web site or in print for Servoy 2.01.
As of Servoy 2.0, the printed and pdf versions of Servoy Developer
Edition User’s Guide has been expanded and separated into two volumes:
Servoy Developer Edition Volume 1: User’s Guide
Servoy Developer Edition Volume 2: Reference Guide
To read a brief description for each of the printed books, go to the
Servoy web Store, scroll to the book you are interested in and click on
the “Info” button.
Marc Norman
Servoy
Hi all,
I’ve listened to Johan and installed 2.0 in a new directory, connected to my pre-existing MSSQL data tables, and connected “repository_server” to my new empty MSSQL database meant to be the new repository. I had already exported my solution (from a Sybase repository).
When I attempt to import, with the “ignore reserved words” checkbox checked, I get a “cannot import” error and the “details” says:
com.servoy.j2db.persistence.RepositoryException: com.servoy.j2db.persistence.RepositoryException: com.sybase.jdbc2.jdbc.SybSQLException: ASA Error -131: Syntax error near ‘date’ on line 1
… followed by the standard warning about reserved words.
Last time this happened, Johan said it was not a syntax error (java message notwithstanding), but a reserved word problem with column/table names (“ignore” checkbox notwithstanding)
I also downloaded Marc’s new book with the list of reserved words at the end. I notice that “date” is indeed a reserved word. Does this mean that “date” as a string cannot be part of a column name … such that, for example, “order_date” is an illegal column name? (to Servoy, if not to MSSQL).
And just so I understand the scope of reserved word issues, “on” is listed a “Servoy reserved word”. If the SQL programmer had created relationships with names like “tblconnection_on_clientid” – are we in trouble?? Or, would “on” be rejected as one of many words in a string used as the message in a message box?
Thanks for any help …
Anne,
In the Troubleshooting section of the Appendix in the Servoy Developer
Edition Volume 1: User’s Guide; and also available in the same section in
Servoy Developer online help (F1):
Troubleshooting: reserved words
Using JavaScript and/or Servoy reserved words in designing a solution
may result in unexpected or negative behavior in using the solution or
Servoy. For a complete listing of JavaScript and Servoy keywords, see
the sections on JavaScript reserved words and Servoy reserved words in
the Appendix of the Servoy Developer Edition Reference Guide.
TIP: While you cannot use reserved words as a complete identity (a
single name of an object), you can concatenate (combine) two (2) or
more reserved words to make a non-reserved name that can be used in
your solution.
Bad:
Reserved words: is, column
Good:
isColumn or is_column
Marc Norman
Servoy
Thanks, Marc. I had missed that the Dev Guide Vol 1 on the site was not the same as the one I downloaded a while back.
I take it that a reserved word as a "complete identity’ used in the string presented to the user in a message box is still a problem, although I don’t think that would be stopping the import, since …
Johan had said to me earlier in this thread, when he thought I was trying to import solution into a Sybase database (I’m not, I’m trying to switch repository from Sybase, to MSSQL):
“first you say that youre db server == ms sql server and then you say that sybase is complaining about a problem that came from sybase..
But this is not the case. You have on youre db server that is build on MS SQL a table with a column that can’t be imported into a sybase server.
it is not a method on line1 or something it is the a sql query that is going wrong that is send to the database because sybase can’t handle a column name you have with ms sql db.”
I take that as Johan interpreting the -131 error as an objection to a column name (vs. any other name or string).
We have 126 tables; I can start comparing that list of reserved words to the column names in our tables; it just seemed out of whack to me that a database could have been created in MSSQL (and used with an Access front end for two years) with column names that MSSQL would not allow.
columns that come from MSSQL should be able to be generated back into MSSQL. But you need to check “Allow reversed keywords” in the import dialog.
I thought you also had MSSQL->Sybase and that sybase did complain.
And then you need to check which column it is.
Hi Johan,
You’re not wrong; originally when I started this thread on May 3, I was trying to move my repository from one computer to another, Sybase to Sybase, while upgrading from 2.0 RC 10 to 2.0. I got “reserved words” errors, and then when I checked the “ignore” checkbox, I got -131 errors.
As of my post on May 6, I had changed to trying for an MSSQL repository, based on the idea that the problem was column names.
I do have the “ignore reserved words” checkbox checked, and still get the -131 error.
For a while, I was concerned that I had not properly reconnected the repository (deleted the old Sybase connection, replaced with connection to new MSSQL database with same connection name), since I didn’t know if the name was what would identify the repository to Servoy. David confirmed for me a couple of days ago that using the same name was the way to do it. So now I believe I have an MSSQL database ready as the new (empty now) repository.
That’s why I was thinking it might be something other than a column name …
In addition to staying with Sybase for my repository, I think I now have to also go back to using the Beta, because back on May 3, after exporting repository from 2.0 RC10, I could not import into new install of 2.0, Sybase to Sybase, even with “ignore reserved words” checked. I got the same errors I am getting with MSSQL to MSSQL.
Thanks for all your help.
Anne