Board index » delphi » Multi users and updates!

Multi users and updates!

    I'm making a software that uses an Access Database,  I've come arross 1
serious problem.  Using a Grid, I'm posting a record that was already
changed by someone else,  my problem is that because it was changed by
someone else in a different software, the program {*word*99}s out and says that I
could not locate the row to update.  I suppose its trying to do a SQL that
matchs the entire row information, and since its no longer the same has
before it complains.
Using the BDE I was able to see the where clause to Key only, but I don't
seem to have this option with ADO,  How to I get around this problem.

Thank you.

Phil C.

 

Re:Multi users and updates!


Quote
>Using the BDE I was able to see the where clause to Key only, but I don't
>seem to have this option with ADO,  How to I get around this problem.

Try
ADODataSet1.Properties['Update Criteria']:=adCriteriaKey;

--
Brian Bushay (TeamB)
Bbus...@NMPLS.com

Re:Multi users and updates!


It says that its readonly, I cannot left assign.    Too bad, it looked
right!

Phil C.

"Brian Bushay TeamB" <BBus...@Nmpls.com> wrote in message
news:k79i5tgvks43dhmlhfrl0renbp4oosbkns@4ax.com...

Quote

> >Using the BDE I was able to see the where clause to Key only, but I don't
> >seem to have this option with ADO,  How to I get around this problem.

> Try
> ADODataSet1.Properties['Update Criteria']:=adCriteriaKey;

> --
> Brian Bushay (TeamB)
> Bbus...@NMPLS.com

Re:Multi users and updates!


Brian,

What event do you write this code for. When I try to do a before post event,
I get "133. Cannot assign to a read-only property"

If fact when I try to run this code any where I still get
'133. Cannot assign to a read-only property'

If you could give us some examples, it would help out alot of people here.

Many Thanks,

RF - ARS Motorola
"Brian Bushay TeamB" <BBus...@Nmpls.com> wrote in message
news:k79i5tgvks43dhmlhfrl0renbp4oosbkns@4ax.com...

Quote

> >Using the BDE I was able to see the where clause to Key only, but I don't
> >seem to have this option with ADO,  How to I get around this problem.

> Try
> ADODataSet1.Properties['Update Criteria']:=adCriteriaKey;

> --
> Brian Bushay (TeamB)
> Bbus...@NMPLS.com

Re:Multi users and updates!


Quote
>What event do you write this code for. When I try to do a before post event,
>I get "133. Cannot assign to a read-only property"

>If fact when I try to run this code any where I still get
>'133. Cannot assign to a read-only property'

>If you could give us some examples, it would help out alot of people here.

here is a Microsoft reference
http://support.microsoft.com/support/kb/articles/Q190/7/27.ASP

--
Brian Bushay (TeamB)
Bbus...@NMPLS.com

Re:Multi users and updates!


Quote
>It says that its readonly, I cannot left assign.    Too bad, it looked
>right!

Maybe if I had given you the correct syntax.
Try
ADODataSet1.Properties['Update Criteria'].value := adCriteriaKey;
--
Brian Bushay (TeamB)
Bbus...@NMPLS.com

Re:Multi users and updates!


AH, Darn,, I should have figured that out...  Damn....  *lowers head in
shame*

Thank you, it works greate!  Thats exactly what I wanted!!  *bows infront of
the master*

Now if only I could figure out how you can read Microsoft's SDK :)

Thanks again,

Phil C.

"Brian Bushay TeamB" <BBus...@Nmpls.com> wrote in message
news:hv8l5t4n2nq8a59gmlr8gaabq8pf0a460n@4ax.com...

Quote

> >It says that its readonly, I cannot left assign.    Too bad, it looked
> >right!

> Maybe if I had given you the correct syntax.
> Try
> ADODataSet1.Properties['Update Criteria'].value := adCriteriaKey;
> --
> Brian Bushay (TeamB)
> Bbus...@NMPLS.com

Re:Multi users and updates!


Ok, this works for Access (Jet Engine), but does it work for SQL Server
2000?

Thanks,
- David Scheidt

"Brian Bushay TeamB" <BBus...@Nmpls.com> wrote in message
news:k79i5tgvks43dhmlhfrl0renbp4oosbkns@4ax.com...

Quote

> >Using the BDE I was able to see the where clause to Key only, but I don't
> >seem to have this option with ADO,  How to I get around this problem.

> Try
> ADODataSet1.Properties['Update Criteria']:=adCriteriaKey;

> --
> Brian Bushay (TeamB)
> Bbus...@NMPLS.com

Re:Multi users and updates!


Quote
>Ok, this works for Access (Jet Engine), but does it work for SQL Server
>2000?

I don't have SQL Server 2000 to test it but I don't see anything in Microsoft's
documentation to indicate it is not supported.

--
Brian Bushay (TeamB)
Bbus...@NMPLS.com

Re:Multi users and updates!


Ok, I set up a simple test.  It works fine for Access using the Jet 4.0
engine.  SQL Server gives the error 'Can't find record'.  It appears to be
ignoring the properity.

- David Scheidt

"Brian Bushay TeamB" <BBus...@Nmpls.com> wrote in message
news:q8ns5t8e7dii8gefdnrl64opducignr300@4ax.com...

Quote

> >Ok, this works for Access (Jet Engine), but does it work for SQL Server
> >2000?
> I don't have SQL Server 2000 to test it but I don't see anything in
Microsoft's
> documentation to indicate it is not supported.

> --
> Brian Bushay (TeamB)
> Bbus...@NMPLS.com

Re:Multi users and updates!


Brian,

I agree with David,

This will work with Access, but will not work with SQL2000.

Are there any other settings that we need to be aware of ???

Thanks

RF - ARS Motorola

Quote
"David Scheidt" <dsche...@hotmail.com> wrote in message

news:3a5f15ad$1_1@dnews...
Quote
> Ok, I set up a simple test.  It works fine for Access using the Jet 4.0
> engine.  SQL Server gives the error 'Can't find record'.  It appears to be
> ignoring the properity.

> - David Scheidt

> "Brian Bushay TeamB" <BBus...@Nmpls.com> wrote in message
> news:q8ns5t8e7dii8gefdnrl64opducignr300@4ax.com...

> > >Ok, this works for Access (Jet Engine), but does it work for SQL Server
> > >2000?
> > I don't have SQL Server 2000 to test it but I don't see anything in
> Microsoft's
> > documentation to indicate it is not supported.

> > --
> > Brian Bushay (TeamB)
> > Bbus...@NMPLS.com

Re:Multi users and updates!


Quote
>I agree with David,
>This will work with Access, but will not work with SQL2000.
>Are there any other settings that we need to be aware of ???

All I can tell you is that it works fine with MSSQL 7.0

--
Brian Bushay (TeamB)
Bbus...@NMPLS.com

Other Threads