11-11-2015 09:25 AM
Can you post a sample screen capture with the schema attached?
11-11-2015 01:18 PM
I don't know what a database schema is. Google helped a bit but still am unsure what you are asking.
Unofficial Forum Rules and Guidelines
Get going with G! - LabVIEW Wiki.
17 Part Blog on Automotive CAN bus. - Hooovahh - LabVIEW Overlord
11-11-2015 01:26 PM
Sorry about that.
@rolfk
Can you post an example with the database schema attached.
11-11-2015 02:20 PM
This might help you and others on what not to use: Access 2007 Reserved Words
11-11-2015 05:09 PM - edited 11-11-2015 05:10 PM
@PatrickLye wrote:
Sorry about that.
Can you post an example with the database schema attached.
Despite the name that could make you expect something else, a schema in database talk is not a graphical drawing of any kind but simply an object container that usually contains tables and stored procedures. There is usually a default schema such as "dbo" for MS SQL Server. A fully qualified column name therefore is specified as {<schema name>].[<table name>].[<column name>] While many (semi-)professional databases don't use any other than the default schema and in that case it is really redundant to specify, for larger databases use of multiple schemas within a database is very common and then it gets important to specify the schema name too to disambiguate the names. There could be a table "Customer" with column "First Name" and otheres in a schema called "Sales" and another schema called "Support".
11-11-2015 05:33 PM
Yes I understand schema. All of mine in SQL server, so far, use dbo. I was just wondering about the SQL string you're using including the schema. I'll play with this a bit.
Thanks
11-11-2015 05:50 PM - edited 11-11-2015 05:51 PM
@PatrickLye wrote:
Yes I understand schema. All of mine in SQL server, so far, use dbo. I was just wondering about the SQL string you're using including the schema. I'll play with this a bit.
Thanks
I see, I misunderstood your use of attached. :-). Because the schema name is prepended I thought you expected some attachment to the post with a drawing or something like that.
The complete identifier would for instance look like this:
[dbo].[Customer].[First Name]
Strictly speaking only
Customer.[First Name]
is required but bracketing every identifier isn't that much more work and saves me the worry about if the square brackets are necessary or not.
12-22-2015 12:50 PM
Hi all,
I have the same error. But it only happens when I run two test consoles at the same time. Any suggestions would be greatly appreciated! Thank you!
Jun
12-22-2015 03:16 PM
@laeagle8 wrote:
it only happens when I run two test consoles at the same time. Any suggestions would be greatly appreciated!
How about don't run two consoles? Lots more information is going to be needed to get much help. Look at my first post. I include complete source code, showing examples of where it worked, and where it didn't, I mentioned what things I tried, and what things I searched for previously, along with details about my database size. You gave very little information, so you will get very little help. Since it doesn't sound like the two issues are related I'd suggest making a new thread where you provide this information.
Unofficial Forum Rules and Guidelines
Get going with G! - LabVIEW Wiki.
17 Part Blog on Automotive CAN bus. - Hooovahh - LabVIEW Overlord
12-22-2015 08:18 PM