Thanks Tony. Obviously I was looking at the view _name_ as the likely problem
but Bill has the answer: all those views depend on other views which may not -
presumably have not since I have a problem - have been created yet.
As Bill must have guessed, I am running my year-end maintenance which recreates
my databases from the bottom up and, hopefully, shows up any errors or problems
that might need attention. The strange thing now is that I have obviously come
across this problem before because for this particular database I have
discovered in my code that I run the file that re-creates my views twice. I
even have these error messages specifically set off:
WRITE 'SET ERROR MESSAGE 2038 OFF' -- Undefined table/view
WRITE 'SET ERROR MESSAGE 2045 OFF' -- Cannot create
WRITE 'SET ERROR MESSAGE 2758 OFF' -- Duplicate table/view
to avoid the errors trying to create a view that already exists. Presumably,
v7.5 or v7.6 tightened up on this as last year when using v7.1 I noticed no
change.
It looks as if I simply need to add:
WRITE 'SET ERROR MESSAGE 2037 OFF' -- Illegal table name
as the reason that the views are created must be due to the second pass through
the file.
I should have noticed this before I posted my question so apologies to all for
an unnecessary question but thanks to Bill for giving me the clue.
Regards,
Alastair.
----- Original Message -----
From: [EMAIL PROTECTED]
To: RBG7-L Mailing List
Sent: Tuesday, January 01, 2008 10:46 PM
Subject: [RBG7-L] - Re: Illegal Table Name error messages.
Just a thought but maybe because a view, when reloaded has to be read as a
select (type of command) it is still seeing the first four characters like in
the older DOS versions .. may not be the case but interesting though
Regards
Tony Luck
"Bill Downall" <[EMAIL PROTECTED]>
Sent by: [EMAIL PROTECTED]
01/01/2008 11:17 PM Please respond to
[EMAIL PROTECTED]
To [EMAIL PROTECTED] (RBG7-L Mailing List)
cc
Subject [RBG7-L] - Re: Illegal Table Name error messages.
Alastair,
Is any of the view definitions referring to another view name, that may not
have been created yet?
Happy New Year!
Bill
On 1/1/08, Alastair Burr <[EMAIL PROTECTED]> wrote:
Can anybody see why any of the following view names should produce the error
message:
Illegal Table Name (2037)
when re-loading? They all fit within the 18 characters max and they all seem
to get re-created properly.
123456789012345678 - 18 max
Artist_Tracks_View
DiscTypeCount_View - reserved word: Disconnect? But table Discs is ok.
Full_HTML_View - reserved word: Full?
LiveAlbums_View
Publishers_View - reserved word: Public?
Reel_to_Reel_View
Thanks in advance for any insight,
Regards & a happy new year to all,
Alastair.
----------------------------
Alastair Burr
St. Albans, UK.
[EMAIL PROTECTED]
-----------------------------
_____________________________________________________________________
This e-mail is confidential. If it is not intended for you please do
not read, distribute or copy it or any attachments. Please notify the
sender by return e-mail and delete the original message and any attachments.
Any views expressed in this e-mail may be those of the individual sender
and may not necessarily reflect the views of Invacare Australia.
_____________________________________________________________________
This e-mail message has been scanned and cleared by MailMarshal at
www.invacare.com.au
------------------------------------------------------------------------------
No virus found in this incoming message.
Checked by AVG Free Edition.
Version: 7.5.516 / Virus Database: 269.17.13/1205 - Release Date: 31/12/2007
15:32
