Article View: pl.comp.bazy-danych.msaccess
Article #137411Błąd 3128 - Access 2013
From: Radosław Biernacki
Date: Fri, 03 Feb 2017 22:15
Date: Fri, 03 Feb 2017 22:15
13 lines
1624 bytes
1624 bytes
Diabeł mnie podkusił żeby się przesiąść. W starszych wersjach kwerenda działała od strzału: DELETE DISTINCTROW lekarze.*, kolejka.IDKOL FROM kolejka RIGHT JOIN lekarze ON kolejka.IDWYS = lekarze.IDLEK WHERE (((kolejka.IDKOL) Is Null)); I dostaję komunikat: Error 3128. Specify the table containing the records you want to delete. Oczywiście da się ominąć ten błąd tworząc dwie kwerendy, ale lekko mnie to wkurza. Czy ktoś z Was to zwalczył?
Technical Details
Message-ID:
<81fac549-1b41-4c31-9964-3774ede517ed@googlegroups.com>Path:
mbox-mo1.pugleaf.net!news-archive.icm.edu.pl!news.icm.edu.pl!news.nask.pl!news.nask.org.pl!news.unit0.net!news.glorb.com!r185no977284ita.0!news-out.google.com!15ni2230itm.0!nntp.google.com!r185no985026ita.0!postnews.google.com!glegroupsg2000goo.googlegroups.com!not-for-mailShow Full Headers
Complete Article Headers
X-Received: by 10.98.88.195 with SMTP id m186mr3665819pfb.16.1486160104215; Fri, 03 Feb 2017 14:15:04 -0800 (PST) X-Received: by 10.157.46.212 with SMTP id w78mr1674825ota.0.1486160104132; Fri, 03 Feb 2017 14:15:04 -0800 (PST) Path: mbox-mo1.pugleaf.net!news-archive.icm.edu.pl!news.icm.edu.pl!news.nask.pl!news.nask.org.pl!news.unit0.net!news.glorb.com!r185no977284ita.0!news-out.google.com!15ni2230itm.0!nntp.google.com!r185no985026ita.0!postnews.google.com!glegroupsg2000goo.googlegroups.com!not-for-mail Newsgroups: pl.comp.bazy-danych.msaccess Date: Fri, 3 Feb 2017 14:15:03 -0800 (PST) Complaints-To: groups-abuse@google.com Injection-Info: glegroupsg2000goo.googlegroups.com; posting-host=178.183.154.123; posting-account=9Fm0dAoAAAD_MxdU7fBVfoEQePK97rMO NNTP-Posting-Host: 178.183.154.123 User-Agent: G2/1.0 MIME-Version: 1.0 Message-ID: <81fac549-1b41-4c31-9964-3774ede517ed@googlegroups.com> Subject: Błąd 3128 - Access 2013 From: Radosław Biernacki <radekb147@gmail.com> Injection-Date: Fri, 03 Feb 2017 22:15:04 +0000 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit