tag:blogger.com,1999:blog-7176045.post112418387735520116..comments2007-03-02T18:29:33.547+03:00Alex Dybenkohttp://www.blogger.com/profile/16954512620659022712noreply@blogger.comBlogger2125tag:blogger.com,1999:blog-7176045.post-1169459912121008222007-01-22T12:58:00.000+03:002007-01-22T12:58:00.000+03:002007-01-22T12:58:00.000+03:00Hi,<BR/>to see what profile used to start access you can use:<BR/>syscmd(acSysCmdProfile)<BR/><BR/>if he really runs access using profile - you have to modify registry settings like described hereAlex Dybenkohttp://www.blogger.com/profile/16954512620659022712noreply@blogger.comtag:blogger.com,1999:blog-7176045.post-1169456935242219602007-01-22T12:08:00.000+03:002007-01-22T12:08:00.000+03:002007-01-22T12:08:00.000+03:00In your post, you have mentioned the Access application with /Profile startup option.<BR/><BR/>Could you advise how I determine if this is the case?<BR/><BR/>I have a client who is suffering this problem and it seems that the only suggested options for the fix are to ensure a correct filename (done that) and to alter the registry settings for this "profile". To be able to walk the client through what needs to be done will save a trip to the other end of the country, so would greatly appeciate any help that you could offer.<BR/><BR/>Sean<BR/>sean[at]fullingdale[dot]comAnonymousnoreply@blogger.com