Many of us have seen, on MSDN, the heading 'Syntax', followed by a rash of nested brackets and keywords, enough to put off the most resolute of code-cutters. However, there is a goldmine of information there, and Phil had an ambition to get at it, and share the gold. The result is this article, full of railroad diagrams.
Hi Sheilish,Only once did I need to get around the limitation of this "dco" security scheme regarding identity_insert where I required strict accountability of the sequential identity numbers (for 1 table in 1 application).If you need to do this you can custom code around it as follows. Unfortunately I don't have a generic solution since […]
A message box appears to me , only with this...Microsoft SQL-DMO(ODBC SQLState : 42000 )An internal consistency error occcurred. Contact Techinal Support for assistance.Backup and restore operation terminally abnormally.ok button...I tried to restore a backup from disk, but the file was restored from a tape.
That message is OK to ignore. It just means that Query analyzer can't display it in the Query By Example (QBE) area. The CASE statements are too complex for it to represent.You'll get similar messages if you create UNION queries, and often if you're doing pivot/crosstab type queries. The query will most likely run ok since […]
Thanks for the link to further details on how to set this up. As it turns out, security on the objects in the Access database were not being enforced. I was able to map to 'Admin' with a NULL password without having to point to the system.mdw file in the registry.CSDunn