[quote="david"]OK, I just read through the entire post to see what the issues are. It seems to me that you have the right idea for the most part but the errors are occurring when you switch your data source from one database platform to another (mssql <--> sybase).
Hi again, David.
Actually, switching the data source from Sybase to MSSQL went without a hitch, a month ago. Repository was still in Sybase, and I would have been happy to stay that way. We had created, in MSSQL, an exact mirror of my Sybase data tables (long story, don't ask -- this project is years old and Servoy is only recently being introduced to it). So switching backends just meant repointing the *data* connection in dbservers, using the same name for the dbserver.
Computer #1 was/is hosting the MSSQL data/database; no problem there. Repository was still Sybase, and no problem there.
Then I wanted to allow a cohort to also work on the solution, and figured I would export the solution, and import it into the repository on the other computer, changing the URL for the data to my IP number. We don't need to work simultaneously.
When I attempted to import into the repository on Computer #2, I got "reserved words" errors, and was told that the Sybase repository didn't like the column and/or table names that the solution referred to (in the MSSQL data tables).
So, my workaround, which we are using as I speak, was to copy my whole bloody Servoy folder onto Computer #2, switch the URL in servoy.properties for the data source to refer to my IP number instead of "localhost", and let my helper go-forr-it. That works; I'm happy.
[Except that even with the .bat file modified to get more memory, it slows to a crawl on her computer after a while ... but that's another thread; a reboot gets her back.]
Then I realized that it'll take an export/import to get myself off the beta and up to the released 2.0. To enable an import, I was advised to convert my *repository* to also be MSSQL.
That brings us up to my first post of today, which can really be summarized into two issues:
1. My original as-yet unanswered question: how does Servoy know which dbserver is the repository. Somehow it knows, because it automatically tries to "use" this dbserver when it launches (or forces you to create one on a new install). I am currently assuming that if one wants to switch the backend for an existing repository, one's only option is to use the identical name as one's original repository dbserver had. If I'm not right on that, then I might have a much bigger problem than "reserved words"; and until someone takes mercy on me and answers that question, we all may be blowing smoke at each other.
2. I have already created an empty MSSQL database that I'm hoping Servoy is seeing as the new repository (see No. 1). I have exported my solution (which refers to MSSQL tables) from the now-defunct old Sybase repository, and would like to import it into the new MSSQL wannabe-repository. I'm still getting reserved words errors, MSSQL to MSSQL.
So Johan says to use the checkbox for ignoring reserved words. I'm left with the impression that Servoy will issue that complaint regardless of circumstances, and that it's a checkbox that should always be checked. No problem with that.
I'll install the 2.0 final release on the other computer (or here, according to Johan), so I can check off that "ignore" checkbox.
And then I'll have my fingers crossed that what I think is a new MSSQL repository actually is.
And if you aren't asleep yet ...
... thanks!
Anne