Yep, it makes sense. Thank you for your contribution, I will make sure it goes to our developers.

Getting it going is not an easy task once a database is installed with the wrong collation. I would actually have preferred the demo to work in case-sensitive mode.



I suggest this:



1) Synchronize the demo code to the installed schema such that there are no variations in case sensitivity (that would fix the problem).



OR



2) Have your install scripts specify a case-insensitive collation. If no collation is specified, the default of the server will be used. Certainly, any collations from other languages let alone case sensitivity collation issues will break the demo. It really should only require a small change to one-line for your install script such that it specifies collation when the database is created. Use the built-in script tool for SQL Server for any of your databases and you should see an example of how the collation is specified (the built-in tool will ensure that collation is included in the script).



NOTE: Once a database is installed with the wrong collation, it requires a very complex script to change it. It is a major task to convert a "server's" default as opposed to setting a default for a "database" (within the server).



So, this was resolved by deleting the database and using a different server. Since, I didn't have access to your install script, I could not properly install it on that server. Thus, my two suggestions above.

Glad you got it going, Trevor.

It can be fixed by specifying the correct collation (I.e Latin1_General_CI_AS) in the install scripts. Any SQL Server instance with a different (I.e. case-sensitive - SQL_Latin1_General_CP1_CS_AS) collation as a server default will fail.

Well, that is a new one for me.



Anyway I am glad at least you found out why it was failing, unfortunately I have no idea how that "case sensitive" stuff can be controlled either by the server or the connection string, hopefully somebody from StrataFrame will be able to comment on this one.

Edhy Rijo

Arghh!!



Okay, hit post by accident.



I changed the case from above from "customers" to "Customers" and it worked.



So, the demo will always fail with any SQL Server instance set to be case-sensitive.

Okay, that is definitely the problem: case sensitivity.



I opened the Visual Studio solution for Role-based Security and tried to open the Customers form. I get the same error: that "customers" is not a valid object. I changed the code from this:

      

public void FillTop100() {

this.FillDataTable("SELECT TOP 100 * FROM Customers");

      }

I have multiple projects with other tools that access the database just fine. I enabled Windows Authentication and tested access to the database.





Consider this:



1) The user account can access that database and get access to SQL Server (I tested named pipes and TCP/IP). The account has been mapped to the database.

2) Again, with the "Browse Dialog Advanced Demo" - After getting the error, The demo WORKS - it accesses the database AND all the records are available.



Hmmm.... I am now wondering if this is a case sensitivity problem. This SQL Server instance is case-sensitive and (just thinking out loud) it appears that the items failing are referencing the wrong case (I.e. customer versus Customer, or rl_role versus rl_Role). I also happened to notice that the browse dialog test will find all the "Smith's" only if I type a search with a capital "S", not a lower-case "s".



looking into it...

You are right so let's try again....



Based on your error:



The customer table is not being found. Make sure your connection string is pointing to the StrataFrameSample database and that the user have rights for this database and try again.

Edhy Rijo

Hi Trevor.

Welcome to the comunity. You will find that people around here are extremely friendly and will do their best to help you out.

One thing that could help at this moment would be to try and get some variables out of the way, so we could concentrate on the StrataFrame features through the demos. Maybe you could set up a testing machine or even a virtual machine and have a fresh install, this way you would have total control of the environment and would certainly be able to run the demos. If you don't mind this, go ahead and we will all be ready to go step by step on the way.

Hope it helps.

Cheers.