[dba-SQLServer] Odd behaviour

there's nothing wrong w/ unbound, in fact w/ an ADP or if you're working 
w/ an MDB and Sql Server, unbound is imnsho the way to go :D

... i think colby is asleep ;o)

Charlotte Foust wrote On 5/14/2004 2:08 PM:

>All unbound?  *My* kind of database! <VBG>
>
>Charlotte Foust
>
>-----Original Message-----
>From: Martin Reid [mailto:mwp.reid at qub.ac.uk] 
>Sent: Friday, May 14, 2004 12:41 PM
>To: dba-sqlserver at databaseadvisors.com
>Subject: Re: [dba-SQLServer] Odd behaviour
>
>
>Francisco
>
>Got it sorted. I am testing with the SQL before moving the whole lot to
>SQL Server. The entire database is run by thousands of SQL Strings. I
>have to follow all the logic first to try and work out whats happening
>with most of the stuff. What calls what etc then build in the specific
>SQL Server Sps oncce I have worked out the logic of how it operates.
>Something like 50000 lines of code in this. I have many of the SPs built
>but cant put them in place until I am 100% sure of the logic used in the
>old application. What clode I can leave in the client and what I MUST
>move to the server. Its a fairly complicated system and theres an
>interface to hand held scanners which will communicate with the new SQL
>Server BE using XML.That should be fun when I get to that section. Its
>actually very interesting as this system in addition to all that has its
>own permissions system which has to remain outisde of SQL Server. Some
>parts are quite hard to get but well we learn something new every day.
>
>The main problem is that when I replace one thing another falls over etc
>so its tail chasing at the moment but getting there.
>
>Oh yeah and its all unbound as well.
>
>Martin
>
>
>
>
>
>----- Original Message ----- 
>From: "Francisco H Tapia" <my.lists at verizon.net>
>To: <dba-sqlserver at databaseadvisors.com>
>Sent: Friday, May 14, 2004 9:30 PM
>Subject: Re: [dba-SQLServer] Odd behaviour
>
>
>  
>
>>Martin,
>>   This sounds like a rights issue.  I'm a bit confused on why you're 
>>using a select in this manner.  By this I mean that it is generally 
>>accepted advice to NOT let users have access directly to tables.  If 
>>your login does not have specific "RIGHTS" to select from a table then
>>    
>>
>
>  
>
>>of course the table won't be visible.
>>
>>
>>
>>Francis Harvey wrote On 5/14/2004 9:02 AM:
>>
>>    
>>
>>>Martin,
>>>
>>>The obligatory note, don't wait too long to turn it into an SP. Now 
>>>that that's out of the way... Is the owner of the table dbo or the 
>>>account that you are logging in as? Is your initial database 
>>>different from the one where your table is stored? If so, you will 
>>>need to use three part notation to specify your table.
>>>
>>>Francis R Harvey III
>>>WB 303, (301)294-3952
>>>harveyf1 at westat.com
>>>
>>>
>>>
>>>
>>>      
>>>
>>>>-----Original Message-----
>>>>From: Martin Reid [mailto:mwp.reid at qub.ac.uk]
>>>>Sent: Friday, May 14, 2004 11:24 AM
>>>>To: dba-sqlserver at databaseadvisors.com
>>>>Subject: [dba-SQLServer] Odd behaviour
>>>>
>>>>
>>>>Working on a major revision to SQL Server
>>>>
>>>>Couple of problems still remaining.
>>>>
>>>>rst.Open ("Select " & argFieldName & " FROM tblDeveloperConsole")
>>>>
>>>>The above line when executed returns an error "Invalid Object Name"
>>>>
>>>>'tblDeveloperConsole'
>>>>
>>>>
>>>>The table is there. SPs work etc etc Am I doing something wrong in 
>>>>how I am trying to create the statement??? I need to pass a field 
>>>>name to the select
>>>>at run time. Well several in fact. The var gets it value OK
>>>>but the SQL
>>>>Statement appears to be correct but isnt.
>>>>
>>>>This will be converted at some point to an SP.
>>>>
>>>>
>>>>Martin
>>>>
>>>>
>>>>
>>>>        
>>>>
-- 
-Francisco