Re: update processor question



Stepping back for a moment it's pretty sad to see the voodoo required
to programmatically create and delete a database.

On one hand it's very easy to create little proggies to do these
functions, and then call to one's own CREATE.MY.ACCOUNT and
DELETE.My.ACCOUNT routines. Write it once and forget about it. A few
minutes of effort eliminates the need to file action items to get some
generic routine that we probably couldn't use anyway. As I usually
say, the tools and source code are there and we should use them.

On the other hand, however - this _is_ after all a database management
system. You'd think that there would be callable functions to create
and delete any sort of database that one would want. I don't mind
stacking some input but the need to stack obscure syntax unique to the
update processor is just stupid.

T
.



Relevant Pages

  • Re: CreateProperty
    ... Whether you are sad or happy, ... Perhaps you meant "add a Table to another Database that you have opened". ... Set tdfEmpHrs = dbLink.CreateTableDef ... Set idxEmpHrs = .CreateIndex ...
    (comp.databases.ms-access)
  • Re: CreateProperty
    ... Whether you are sad or happy, ... Perhaps you meant "add a Table to another Database that you have opened". ... Set tdfEmpHrs = dbLink.CreateTableDef ... Set idxEmpHrs = .CreateIndex ...
    (comp.databases.ms-access)
  • Re: Query SQLServer
    ... I'm sad to confirm that. ... could have access to the database with the purpose ... Is there any dirty, ... You might want to look for another host, or get a VPS and do it yourself. ...
    (comp.lang.php)
  • Re: Query SQLServer
    ... I'm sad to confirm that. ... could have access to the database with the purpose ... my host does not install any extra software. ... Is there any dirty, ...
    (comp.lang.php)
  • RE: HOWTO programmtically code use in T-SQL
    ... but I have found the sad answer. ... I found an rticle posted by a Gary Johnson who was trying to solve the ... one can not pass a variable into the "use database" ... was a programmatic way of changing a connection "currently being used" ...
    (microsoft.public.sqlserver.programming)