Hi Adrian
I had missed that bit. That makes sense now.
Cheers
Phil Jackson
On 6/30/2010 5:04 PM, Adrian Klaver wrote:
On Thursday 01 July 2010 11:11:29 am Phil Jackson wrote:
Hi Adrian
The link says that;
"Identifier and key word names are case insensitive."
But I have renamed the sour
Adrian Klaver writes:
> On Thursday 01 July 2010 11:11:29 am Phil Jackson wrote:
>> The link says that;
>> "Identifier and key word names are case insensitive."
>>
>> But I have renamed the source table in lowercase and this gets me one
>> step further.
> You need to go to bottom of that section
On Thursday 01 July 2010 11:11:29 am Phil Jackson wrote:
> Hi Adrian
>
> The link says that;
>
> "Identifier and key word names are case insensitive."
>
> But I have renamed the source table in lowercase and this gets me one
> step further.
>
> I'll carry on and see what happens next.
>
> Cheers
>
Hi Adrian
The link says that;
"Identifier and key word names are case insensitive."
But I have renamed the source table in lowercase and this gets me one
step further.
I'll carry on and see what happens next.
Cheers
Phil Jackson
On 6/30/2010 3:18 PM, Adrian Klaver wrote:
On 07/01/2010
On 07/01/2010 09:46 AM, Phil Jackson wrote:
We've set up a Sql database for the first time and get an error reported
back to our application from the ODBC session object when we try to open
one of the tables.
[42p01][7]ERROR Relation "SqlAnal" does not exist; table not found!
Here is my databas
We've set up a Sql database for the first time and get an error reported
back to our application from the ODBC session object when we try to open
one of the tables.
[42p01][7]ERROR Relation "SqlAnal" does not exist; table not found!
Here is my database outline in the Admin tool
Servers(1)
Co
