Do you know why a ADOX Catalog View created a procedure not a view?

[mjk9564]

The last programmer here wrote some reporting software that uses a ADOX Catalog. He creates a SQL query then sets to a command object, then sets the catalog.views = queryname, command object last he sets the recordset = queryname. After the user closes the report viewer it deletes the created view.

One of our customers was getting an error saying the query was already created. I searched all views and tables and no query was listed with that name. On a wim I checked the procedure container at it was in there. I deleted it and it works fine now.

Does anyone know why it would of made a procedure instead of a view?

I have since changed the module for this customer where it doesn't use catalogs only recordsets that just create a temp query then close, so nothing to delete now. But, we are trying to decide if this is something we should update with all our customers or is it something that is isolated. If any of you have heard of anything like this please reply.

Thanks,
Matt

 

[DirectDrive]

this is a long shot but is it possible that the code tried to make a view with the same name of a sproc that already existed?