how does DataMgr handle SQL Server tables with different owners?

[DaveBurns]

When I give a DataMgr function a table name, it doesn't seem to like
it when I specify the owner. It tells me the table doesn't exist. My
current code uses raw SQL and I frequently have to qualify table names
with their owner (a la "ownername.tablename") because different tables
were created with different owners. Everything seems to work with
DataMgr if I simply remove the owner name. For various reasons, my
code uses a different account name to log into my test bed's database
than it does into my production database. Does anyone know if not
qualifying the table name going to cause an issue when I move from my
dev box to my production box? Is there a smart way to handle this with
DataMgr that I didn't see in the doc?

Thanks,
Dave

[Steve Bryant]

Dave,

I actually didn't think about owners when I created DataMgr as all of
my tables always have the same owner.

I could add a method to indicate the owner for a table or auto-detect
the owner from a table name if it is given with dot in the table name.

What do you think?

Steve

[DaveBurns]

Steve - Hmm, those might be useful functions. But my main question is
whether or not I need to worry about table owners at all given that I
do need to when I use raw SQL (say, in SQL Server Management Studio or
in my current code). Does DataMgr ensure that I don't have to worry
about that? That'd be nice.

Dave

[Steve Bryant]

Dave,

DataMgr currently executes the code without the owner in the SQL. So,
unfortunately, I would think that would be a concern. That is
certainly something I will look into though.

Sorry,

Steve