Forum Replies Created

Viewing 9 posts - 1 through 9 (of 9 total)

  • RE: Setting a variable to the results of an Exec () statement

    Hi All,

    Another tested variation which works.

    DECLARE

    @Ticketvalue integer,

    @Identification varchar(100)

    SET @Identification = 'identity string'

    SELECT @Ticketvalue = Ticketnum

    FROM

    (select * from

    openquery(LINKSERVER,'select Ticketnum,RowID from TABLE1')t1)t2

    WHERE RowID = @Identification

    select @Ticketvalue

  • RE: OPENDATASOURCE(Microsoft.Jet.OLEDB.4.0)

    Hi All,

    Don't think this is a TSQL matter any longer and not sure how to move it to the correct forum.

    You were both right about permissions.

    Tests show that user credentials...

  • RE: OPENDATASOURCE(Microsoft.Jet.OLEDB.4.0)

    Hi Andy and Noel,

    Really appreciated your suggestions.

    New test interesting?

    QA on BOX2 connected to SQL Server on BOX1 calling AccessDatabase on BOX1 = Success.

    Very puzzling.

    Best regards,

    Ian

  • RE: Can someone help me parse a free text field

    Hi Steve,

    I was preparing a parser for you while Andy posted the better solution.

    Anyhow, if you can't predict the literals each time, here is the parser I wrote: (assuming no drug...

  • RE: OPENDATASOURCE(Microsoft.Jet.OLEDB.4.0)

    Hi Andy,

    Previously tried SQL Server 2000 (itself) on privilaged service account, to no avail.

    Probably not applicable however SQLSERVERAGENT (on both boxes) runs on domain service account with read/write to the...

  • RE: I have multiple Cascade update problem in SQL server 2000

    Hi Ranjeet,

    I shall leave answers to the experts, except to mention that your problem seems to stem from your table structures.

    I think, if you correctly identify your entities/elements and normalise it...

  • RE: OPENDATASOURCE(Microsoft.Jet.OLEDB.4.0)

    Perhaps I should have mentioned...

    These tests in QA replicate a real problem in production, when said OPENDATASOURCE had been working for a year in my application SQL report modules, using token...

  • RE: OPENDATASOURCE(Microsoft.Jet.OLEDB.4.0)

    Hi Noel,

    1. NO - as seen from the provider string, this is a database password, not a workgroup.

    2. YES - nobody else has the DB open.

    3. NO - there are...

  • RE: OPENDATASOURCE(Microsoft.Jet.OLEDB.4.0)

    Thank you Noel however this is not the case.

    DisallowAdHocAccess = 0 and all patent accounts have access, otherwise it would not work at all i.e. when QA is connected to SQL Server...

Viewing 9 posts - 1 through 9 (of 9 total)