Hi,

I get this error message whenever I try to View\Document Source.

It occurs for all databases, and the ones under immediate consideration
are in any case either paradox or ansi ascii. It just has happened all of
a sudden (well, a week since I last accessed the code).

The data is all lower order, and I type plain english code.

Could this be related to something outside of paradox, perhaps an
installation of small utility with dated .dll or something? I am running
pdox9 under XP.

Thanks for any tips. Bertil's "Error's Explained" does indicate that this
is related to the tables, but a half dozen databases cannot all have this
problem at once, can they?

-----
Anne Wainwright
Please reply to group

Hi.

To add to previous message

Anne Wainwright <duffaddress (AT) ananzi (DOT) co.za> wrote

"261 Character(s) not supported by Table Language."

... & I should say that it is preceded by a Paradox warning

X Unexpected General Protection Violation
Press OK then save your documents and exit Paradox
If problem persists, press Abort to terminate Paradox



-----
Anne Wainwright
Please reply to group

Anne

View | Document source creates a table PAL$SRC. I guess this table is
created with the language driver defined in BDE Admin. The table contains
all code from your forms. Comments included. This should be enough
information for you to find out what's happening.




--
Bertil Isberg - CTECH
Paradox buglist:
online: http://web.comhem.se/~u82608896/

"Anne Wainwright" <duffaddress (AT) ananzi (DOT) co.za> skrev i meddelandet
news:Xns9784C16A43A7azopane (AT) 196 (DOT) 25.240.158...

Anne,
Each times you get an error in two parts (windows)
the first part comes from Paradox
the second part from the BDE

So that seems to confirm Bertil advice about a problem in your BDE table
definition.

Régis

Bertil, hi,

thanks for the tip. I looked very closely at the issue of table language
settings in the BDE and the tables proper but to no avail. Note that
this all of a sudden affected every single database that I had. I created
a form with a button and nothing other than the default code, still the
same problem.

At this stage the problem had devolved to the Paradox GPF mentioned in my
follow-up to the initial post.

It was solved thanks to a tip from Gunter while we chatted on #paradox on
Paradox Day, which seemed to tie in with solutions to other printing
problems reported with pdox9 and XP as I scoured google groups.

The solution was to delete all the printers. Trust me when I say that
doing this immediately after validating the problem resulted in an
immediate clearing of the problem.

Pity that I didn't delete them one at a time (6, including one 'Auto'
whatever that may be). But the solution was very welcome.

Regards
Anne

"Bertil Isberg" <bertil.isberg@NOcomhemSPAMdotse> wrote in
news:44147be0 (AT) pnews (DOT) thedbcommunity.com:



--
-----
Anne Wainwright
Please reply to group