Adam


The only things I can spot are the two name changes and as long as they reflect what's on disk you should be OK. You're using the default logon so you should have full access, but at this stage I'd start checking just to make sure that this hasn't accidentally been altered and you no longer have the privileges you think you have.

If its not to big / confidential the only other thing I can suggest is post / email the lot and let me have a shuftie.

On the positive side people have been asking for a read only version so if you can sus this you could be on a nice little earner

Roy Lambert [Team Elevate]

Adam,

<< At my clients on a XP machine. Testing it here in the office is Vista.
(We have tried doing a right-click on EDBManager and chosing 'Run as
Administrator', but still can't edit the data). >>

What directory are you using for the database ?  If you want, you can also
contact me via Skype and we can do a remote desktop.  I can usually find the
solution to this type of problem pretty quickly that way.

It's got me beat as to why they're read only. Could it be that we designed
and made the database on one machine (my development machine) and then
copied the data directories to another machine and tried to run? (is this a
no-no with EDB, or could it have caused problems with the Read Only)? >>

No, you can copy around databases, provided that you copy everything
including the database catalog.

--
Tim Young
Elevate Software
www.elevatesoft.com

Hi Roy,

> The only things I can spot are the two name changes and as long as they
> reflect what's on disk you should be OK. You're using the default logon so
> you should have full access, but at this stage I'd start checking just to
> make sure that this hasn't accidentally been altered and you no longer
> have the privileges you think you have.
>
> If its not to big / confidential the only other thing I can suggest is
> post / email the lot and let me have a shuftie.

No problems at all - the data only contains test data at the moment, and
have posted the database up on the binary forums.

I have to head off overseas shortly though, so if I stop replying to the
posts, it's not becaues I'm being rude.

> On the positive side people have been asking for a read only version so if
> you can sus this you could be on a nice little earner

I love a bloke who can see the silver lining!  

Cheers

Adam.

Hi Tim,

> What directory are you using for the database ?  If you want, you can also
> contact me via Skype and we can do a remote desktop.  I can usually find
> the solution to this type of problem pretty quickly that way.

Thanks for the offer. I have a dodgy internet connection at work at the
moment (which unfortunately has killed VOIP) and it's my last day before I
fly out of the country, so I might wait until I come back in a couple of
weeks (if we haven't been able to determine the problem before then).

> It's got me beat as to why they're read only. Could it be that we designed
> and made the database on one machine (my development machine) and then
> copied the data directories to another machine and tried to run? (is this
> a no-no with EDB, or could it have caused problems with the Read Only)? >>
>
> No, you can copy around databases, provided that you copy everything
> including the database catalog.

Basically the same as DBISam then, so it's not that. I have placed a copy of
the database on the binaries newsgroup per Roy's request. Everything appears
to be right for me.

Off the top of my head we've tried:

Right-clicking EDBMGR.exe and choosing 'Run as Administrator' (in Vista)
Tried on various drives
Tried on various computers (both Windows XP and Vista)
Tried over network, and on local HDD's.
Checked the Priveledges on the database (as best as I know how)...

.... and can't get it to allow us to edit the tables. (We're using EDBMgr
1.09 Build 4).

The only machine we can alter the tables on is the original development
machine. Hopefully you're able to find something in there I've done wrong...

Cheers

Adam.

Adam

>I have to head off overseas shortly though, so if I stop replying to the
>posts, it's not becaues I'm being rude.

That's good cos I'll have to install 1.09 on a PC. Already tried opening in V2 and no go.

Roy Lambert [Team Elevate]

Adam


Some good news, some bad news.

Well I can now confirm the read only nature of the database, and can find no reason for it (Tim probably can but not me). The good news is that what you can do is reverse engineer it including the data, and run that script to create editable tables.

Roy Lambert

Adam,

Sorry for the delay in getting back to you.  I got a little swamped on
support issues toward the latter part of the week.

<< No problems at all - the data only contains test data at the moment, and
have posted the database up on the binary forums. >>

The database, by itself, is perfectly editable here.  What I did was extract
your database into a specific directory, and then add a new database that
uses this directory as its path using CREATE DATABASE.  I used an existing
configuration.  More than likely the issue that you're experiencing is this
one:

http://www.elevatesoft.com/incident?action=viewrep&category=edb&release=2.02&type=f&incident=2968

And, this would still be present as a bug in 1.09, of course.

--
Tim Young
Elevate Software
www.elevatesoft.com

Tim


I should have remembered that one

Roy Lambert

Good Morning Tim and Roy,

Thanks for your replies and sorry for the late response. (I've been sunning
myself in Vanuatu doing some very nice Diving on a WWII wreck!)  

I'll look at reverse engineering the database to correct the current
problem, but was wondering - is there any possibility thta this will be
fixed in a later version of EDB 1.x, or will I need to upgrade to EDB 2 to
stop this from occurring again?

Cheers

Adam.

> Sorry for the delay in getting back to you.  I got a little swamped on
> support issues toward the latter part of the week.
>
> << No problems at all - the data only contains test data at the moment,
> and have posted the database up on the binary forums. >>
>
> The database, by itself, is perfectly editable here.  What I did was
> extract your database into a specific directory, and then add a new
> database that uses this directory as its path using CREATE DATABASE.  I
> used an existing configuration.  More than likely the issue that you're
> experiencing is this one:
>
> http://www.elevatesoft.com/incident?action=viewrep&category=edb&release=2.02&type=f&incident=2968
>
> And, this would still be present as a bug in 1.09, of course.
>
> --
> Tim Young
> Elevate Software
> www.elevatesoft.com
>

Adam,

<< Thanks for your replies and sorry for the late response. (I've been
sunning myself in Vanuatu doing some very nice Diving on a WWII wreck!)  
>>

Cool.

<< I'll look at reverse engineering the database to correct the current
problem, but was wondering - is there any possibility thta this will be
fixed in a later version of EDB 1.x, or will I need to upgrade to EDB 2 to
stop this from occurring again? >>

Unfortunately we're not doing any more updates to EDB 1.x at this time.

--
Tim Young
Elevate Software
www.elevatesoft.com