Due to time constraints, more than two months since problem was raised, our
Help Desk department decided to reinstall all the software applications on
the computer. The problem is gone now.

Kind regards,

Tony Perez

Now MS Access crashes every time I try to switch to my Release branch. I've
done a compact and repair (still crashes) and rebooted my workstation
(still crashes). How do I move between branches and trunk if it crashes?

I set up SVN CSS proxy using SVN protocol on localhost. Loading projects
from repository is working fine, but when update new files (objects) from
local source to repository error occured "

---------------------------
SVN error
---------------------------
COM.SvnClient.Error, HRESULT=0x80020009
Commit failed (details follow):
Authorization failed
---------------------------
OK
---------------------------

my repositry URL: svn://localhost/ -- repository is published on IIS with
host localhost.

see attachment ...

We are using a Collabnet Subversion server version 1.6 and tortoise svn
version 1.6 client. When using Tortoise SVN to update the PBL's outside of
powerbuilder, this is at an acceptable rate. When logging into
powerbuilder, this becomes horribly slow, taking 1-2 hours to finish. We
are using push ok version 1.6.17.0 and Powerbuilder 12.

From this previous ticket,
http://www.pushok.com//tickets_addmodify.php?id=1836

It was reported that enabling Share Objects is not possible due to
architectural considerations.

I would like to suggest that I believe this can be done. To illustrate how
you can achieve this goal, try the following steps:

1) Create a new Access database. Call it "Template" and save it in a path
like "C:\AccessDemo\Template\". Add it to SVN into a new repository, call
it "Template". Create few objects to get added to SVN. Close the Template.

2) Open Access but instead of Creating or Open a database, dismiss File
menu, go to the Source Code tab and click button "Create From PushOk SVN
Proxy". ON the dialog, select Template as the repository but change the
local path to "C:\AccessDemo\Project1\".

3) Repeat #2 but use path "C:\AccessDemo\Project2\"

Now we have 3 folders that all uses same repository, but additional options
are needed. On the ribbon, in Source Control tab, select Options and set
following options:

Add object to source control when you add them to Microsoft Access? { No
(or Ask) }
Remove object to source control when you delete them from Microsoft Access?
{ No (or Ask) }

Click OK. You are now able to have Project1 and Project2 diverge and their
own customs objects (not checked into SCC at all) but also share some of
objects which also can be added via "Add Objects to PushOk SVN Proxy".

That may then give you a structure which you can then study to see how
"Share Objects" could be implemented so multiple Access database files can
share a common components and not necessarily have everything that's stored
in the shared repository neither add everything within each file into the
repository.

I hope the above suggestion give you enough information & insights to
enable Share Objects functionality and thus simplify management of shared
objects.

Thanks!

Unable to integrate Adobe Robo Help 9 with cvsscc_2206.msi, Push ok

unable to integrate it with robo help 9. please do the needful on
priority.