Re: Problem with name of table

Dan Anderson wrote:
> dbase+  I am writing a website application for retail insurance agents to 
> use to request policy changes (we call them endorsements).  Throughout the

> process I have named my programs and my datatables so they will be grouped

> together by starting each name with "endt" which is short for
endorsement. 
> I have built the programs little by little adding a different type of 
> potential endorsement only after the last one is working completely.  My 
> main table is called "Endorsements.dbf" and my line detail table
is called 
> "EndtDetails.dbf."  Yesterday afternoon the programs would no
longer deal 
> with a table name "EndtDetails.dbf."  The line to make the query
active 
> generates:
> Error Code: 239
> 
> Database Engine Error: Unknown internal operating system error.
> 
> My first reaction was to assume something had corrupted my datatable; so, I

> rebuilt it and started again.  But it always generated the same error.  So
I 
> tried renaming another table EndtDetails.dbf and continued to get the same

> error.  Then I tried renaming the original EndtDetails.dbf to Details.dbf.

> The programs have no problem using the old table under a different name. 
By 
> the way, all the programs that used EndtDetails.dbf now reject any
reference 
> to the name.
> 
> What on earth would cause everything to start rejecting a particular table

> name when it had shown no problems in the past?  And how can I be sure this

> kind of thing won't happen again?

What is the table level defined in the BDE Administrator? If it is not 
level 7, then this is most likely the problem ... especially if it is 
level 4 or less ... table names have maximum lengths in those versions. 
However, I've never heard of that particular error before, and this is 
just a guess.

Ken

-- 
/(Opinions expressed are purely my own, not those of dataBased
Intelligence, Inc.)/

*Ken Mayer* [dBVIPS]
/Golden Stag Productions/
dBASE at goldenstag dot net
http://www.goldenstag.net/GSP
http://www.goldenstag.net/dbase/dBASEBooks.htm

dbase+  I am writing a website application for retail insurance agents to 
use to request policy changes (we call them endorsements).  Throughout the 
process I have named my programs and my datatables so they will be grouped 
together by starting each name with "endt" which is short for
endorsement. 
I have built the programs little by little adding a different type of 
potential endorsement only after the last one is working completely.  My 
main table is called "Endorsements.dbf" and my line detail table is
called 
"EndtDetails.dbf."  Yesterday afternoon the programs would no longer
deal 
with a table name "EndtDetails.dbf."  The line to make the query
active 
generates:
Error Code: 239

Database Engine Error: Unknown internal operating system error.

My first reaction was to assume something had corrupted my datatable; so, I 
rebuilt it and started again.  But it always generated the same error.  So I 
tried renaming another table EndtDetails.dbf and continued to get the same 
error.  Then I tried renaming the original EndtDetails.dbf to Details.dbf. 
The programs have no problem using the old table under a different name.  By 
the way, all the programs that used EndtDetails.dbf now reject any reference 
to the name.

What on earth would cause everything to start rejecting a particular table 
name when it had shown no problems in the past?  And how can I be sure this 
kind of thing won't happen again?


-- 
Dan Anderson
UBI Processing Dept.
andersond@ubinc.com
800-444-4824 ext 101 

The table is level 7

-- 
Dan Anderson
UBI Processing Dept.
andersond@ubinc.com
800-444-4824 ext 101
"Ken Mayer [dBVIPS]" <dbase@_nospam_goldenstag.net> wrote in
message 
news:qm$qTdOZIHA.1532@news-server...
> Dan Anderson wrote:
>> dbase+  I am writing a website application for retail insurance agents
to 
>> use to request policy changes (we call them endorsements).  Throughout

>> the process I have named my programs and my datatables so they will be

>> grouped together by starting each name with "endt" which is
short for 
>> endorsement. I have built the programs little by little adding a 
>> different type of potential endorsement only after the last one is 
>> working completely.  My main table is called
"Endorsements.dbf" and my 
>> line detail table is called "EndtDetails.dbf."  Yesterday
afternoon the 
>> programs would no longer deal with a table name
"EndtDetails.dbf."  The 
>> line to make the query active generates:
>> Error Code: 239
>>
>> Database Engine Error: Unknown internal operating system error.
>>
>> My first reaction was to assume something had corrupted my datatable;
so, 
>> I rebuilt it and started again.  But it always generated the same
error. 
>> So I tried renaming another table EndtDetails.dbf and continued to get

>> the same error.  Then I tried renaming the original EndtDetails.dbf to

>> Details.dbf. The programs have no problem using the old table under a 
>> different name.  By the way, all the programs that used EndtDetails.dbf

>> now reject any reference to the name.
>>
>> What on earth would cause everything to start rejecting a particular 
>> table name when it had shown no problems in the past?  And how can I be

>> sure this kind of thing won't happen again?
>
> What is the table level defined in the BDE Administrator? If it is not 
> level 7, then this is most likely the problem ... especially if it is 
> level 4 or less ... table names have maximum lengths in those versions. 
> However, I've never heard of that particular error before, and this is 
> just a guess.
>
> Ken
>
> -- 
> /(Opinions expressed are purely my own, not those of dataBased
> Intelligence, Inc.)/
>
> *Ken Mayer* [dBVIPS]
> /Golden Stag Productions/
> dBASE at goldenstag dot net
> http://www.goldenstag.net/GSP
> http://www.goldenstag.net/dbase/dBASEBooks.htm
> http://www.goldenstag.net/dbase 

Dan Anderson wrote:
> The table is level 7
> 

Well, it was a guess. I just created a table "EndtDetails.dbf". I was

able to open it, modify it, put it on a form, run the form, etc. with no 
problems. I am not currently set up to do any web testing, but I am not 
sure why you're getting this issue.

Ken

-- 
/(Opinions expressed are purely my own, not those of dataBased
Intelligence, Inc.)/

*Ken Mayer* [dBVIPS]
/Golden Stag Productions/
dBASE at goldenstag dot net
http://www.goldenstag.net/GSP
http://www.goldenstag.net/dbase/dBASEBooks.htm

In article <pDLP6IOZIHA.1532@news-server>, andersond@ubinc.com says...
> dbase+  I am writing a website application for retail insurance agents to 
> use to request policy changes (we call them endorsements).  Throughout the

> process I have named my programs and my datatables so they will be grouped

> together by starting each name with "endt" which is short for
endorsement. 
> I have built the programs little by little adding a different type of 
> potential endorsement only after the last one is working completely.  My 
> main table is called "Endorsements.dbf" and my line detail table
is called 
> "EndtDetails.dbf."  Yesterday afternoon the programs would no
longer deal 
> with a table name "EndtDetails.dbf."  The line to make the query
active 
> generates:
> Error Code: 239
> 
> Database Engine Error: Unknown internal operating system error.
> 
> My first reaction was to assume something had corrupted my datatable; so, I

> rebuilt it and started again.  But it always generated the same error.  So
I 
> tried renaming another table EndtDetails.dbf and continued to get the same

> error.  Then I tried renaming the original EndtDetails.dbf to Details.dbf.

> The programs have no problem using the old table under a different name. 
By 
> the way, all the programs that used EndtDetails.dbf now reject any
reference 
> to the name.
> 
> What on earth would cause everything to start rejecting a particular table

> name when it had shown no problems in the past?  And how can I be sure this

> kind of thing won't happen again?
> 


Dan,

Can you show us the QUERYs involved in this problem?

Did you try rebooting the PC? Maybe the BDE was messed up and it wasn't 
dBASE at all.

-- 
Geoff Wass [dBVIPS]
Montréal, Québec, Canada

.|.|.|        dBASE info at http://geocities.com/geoff_wass       |.|.|.
.|.|.| ---------------------------------------------------------- |.|.|.