dotSoftwaredotDevelopmentdotCustomersdotAbout us
PushOk logoblank
bullet Home
bullet My software
bullet Support
bullet My payments
bullet My info
bullet Subscriptions
bullet Voting
bullet Contact us
fast linksFast Links
news&eventsnews and events

2012-12-21 
Major update of SVN SCC plug-in - versions 1.7.2 are finaly released

2012-12-21 
Major update of SVNCOM version 1.7.2 are finaly released

Lightweight embedded Node.js database with MongoDB API.

Ticket

Search go
PushOk Logo blank
leftTicketright

Cannot login - username field always blank and disabled

( SVNSCC , ms access 2003, Latest, WIN 2000/XP  )
Type: Public Status:Closed Created: 07 Sep 05 09:00 Updated: 02 Feb 06 02:00
--> Igor Pushkov (admin)  at 02 Feb 06 02:00 writes

All mentioned above should be fixed in new version 1.3.
--> Paul Coddington (user)  at 09 Sep 05 09:00 writes

Additional problems found:

1. Plugin does not remember list of URLs (why doesn't any subversion tool
give us a visual interface for the repository - arrgh!).

2. Initial attempt to login and connect is successful, but when attempt to
create the project it fails with 'unable to retrieve password'.

3. From that point on, it is impossible to login - it just asks over and
over again forever with no error message.

So, in summary, I am having showstoppers in both Office 2003 and VS.NET
2003. This is a very promising tool, which I would like to support, but
for my current environment, for some reason or another, it is behaving like
an early Alpha with too many bugs to be useable.

--> Paul Coddington (user)  at 07 Sep 05 09:00 writes

Ok - solved this one. Seemed to work OK after running VS.NET 2003 for the
first time with the plugin. Also, issue with tables not being able to be
checked out cropped up but discovered that you need the sandbox option as
JET engine does not support folders beginning with ".svn".

However, several new issues are discovered which are going to make life
very difficult:

1. Spurious notification that a file has been been removed/renamed from the
project that must be cancelled when checking tables in and out
(intermittant). Not sure what I will lose if I disable that permanently
(bear in mind I also work in VS.NET as well as MS Office).

2. Macro security must be set to low if the project has no certificate as
the warning dialog really mucks up the plugin (otherwise every time
checking in and checking out the warning appears).

3. MOST SERIOUS: You must always resolve all checkout and changes before
closing the database (not always possible, and tough luck if it crashes).
Why? Because if you reopen it, it disables SCC because it *wrongly* thinks
it is already worked on by another user (with the same username as
yourself). This really needs to be fixed to be viable and is the only
thing in the way of purchase as far as I can see. It does not register the
fact the your username is the same as the one it is worried about.
--> Paul Coddington (user)  at 07 Sep 05 09:00 writes

Trialling plugin in MS Office 2003 and VS Studio .NET 2003.

As people are discussing using it for Access, presume this is OK (it must
be if the SCC API is properly supported).

However, when I attempt to work with a project, the login dialog appears
with a blank username field which is disabled, so I can't log in. Only the
password field is available to type in, but that alone does not work (that
is, it is not passing my windows login name, it really is blank).

What have I missed?
Rate this ticket:
Not useful at all
Partially useful
Useful
Very useful



You are 9552457 visitor since 20 Jan 2003.
909 visitors today and 6 online right now.
blank left to top right blank

© Copyright by PushOk Software, 2003-2024, webmaster@pushok.com