July 24, 2008 01:21pm pdt

1. rfwoolf 31,325
2. developm... 18,977
3. SteveBay 16,875
4. kretzsch... 9,850
5. ziolko 9,800
6. NickUpson 7,275
7. Geert_Gr... 6,830
8. dinilud 5,348
9. TheRealL... 5,100
10. RickJ 5,000
11. aikimark 3,664
12. MerijnB 3,620
13. Johnjces 3,100
14. mikelittlew... 2,975
15. mankowitz 2,500

1. kretzsch... 56,131
2. developm... 43,302
3. rfwoolf 38,050
4. ziolko 28,095
5. mnasman 26,360
6. dinilud 18,298
7. SteveBay 17,875
8. emoreau 16,735
9. TheRealL... 16,252
10. NickUpson 15,707
11. Workshop... 14,869
12. mikelittlew... 14,336
13. angelIII 13,995
14. calinutz 12,000
15. TimCottee 10,824

02.04.2008 at 01:52PM PST, ID: 23136432 | Points: 500

	[x] Attachment Details

What / When (is the) / (can i expect the) danger of record lock

Zones: Miscellaneous Software, Delphi Programming, Delphi Database

Tags: MS, MS Access, MS Access 2007, Delphi Application

I have a delphi application that uses an Access database (MS Access 2007). I know "boo hisss" but after all that, I need to know under what circumstances would there be a record locking issue? If, through the application, two or more different users attempted to access / update the same record what would be some of the possible disaterous results? Is there any way to
(aside from upgrading to a database that isn't free) prevent record locking issues? Would using client data sets help to solve any potential record locking issues?

Start your free trial to view this solution

Question Stats

Zone: Programming

Question Asked By: mikesExpertExchange

Question Asked On: 02.04.2008

Participating Experts: 3

Points: 500

Translate:

Loading Advertisement...

20080236-EE-VQP-29 / EE_QW_2_20070628