| From: | "Mihai Gheorghiu" <tanethq(at)earthlink(dot)net> |
|---|---|
| To: | <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Corrupted tables? |
| Date: | 2001-08-01 14:14:28 |
| Message-ID: | 002f01c11a94$4b518440$6e646464@New6.Travel |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Addendum:
I double-checked:
- It is the tables that were included in the MSAccess querry that can no
longer be accessed by MSAccess.
- The tables in question can be viewed with psql and PGAccess.
Is there a way to save the work or do I have to re-create and re-export
data?
Any suggestions are highly appreciated.
Mihai
-----Original Message-----
From: Mihai Gheorghiu <tanethq(at)earthlink(dot)net>
To: pgsql-general(at)postgresql(dot)org <pgsql-general(at)postgresql(dot)org>
Date: Tuesday, July 31, 2001 5:47 PM
Subject: [GENERAL] Corrupted tables?
>Is there anything like that?
>I was exporting some MSAccess tables via ODBC, and it was taking a long
>time.
>I tried to do something else in the mean time (open Forte).
>The export ceased and I started to get "ODBC connection failed".
>If I open a blank MSAccess db and fill it with new files by linking to the
>PG db, it works. Then I try to open them one by one, and some open, some
>don't (it seems those that were accessed in the query that was running at
>that moment).
>Is there a way of repairing PG tables?
>
>Thank you all,
>
>Mihai
>
>
>---------------------------(end of broadcast)---------------------------
>TIP 3: if posting/reading through Usenet, please send an appropriate
>subscribe-nomail command to majordomo(at)postgresql(dot)org so that your
>message can get through to the mailing list cleanly
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Gunnar Rønning | 2001-08-01 14:14:29 | Re: When PostgreSQL compliant JDBC 2.0? |
| Previous Message | Tom Lane | 2001-08-01 14:11:22 | Re: Finding number of current connections |