MS Access Multiuser - Avoid errors when 1 of 2 BackEnds is not found

Author

Avoid errors when 1 of 2 BackEnds is not found

Alp Bekisoglu

2006-02-06, 7:24 am

Hi Experts,

Might sound a bit confusing but; I'm trying to use A2K db FE/BE but with 2
backends. One is more sensitive data (financial) which I need to keep
undistributed. In the main server both will be present (head office). But
for the branch office the #2 BE will not be copied. I am using Peter
Vukovic's Reconnect() function to ensure proper be connectivity.

The scenario is when the second BE is not present, all related forms are
inaccessible too so if I can rid any errors on Reconnect, I should be safe.
Even the related menu options are unavailable when db accessed by machines
outside the scope.

Is this do'able via VBA? If so, any help/pointers is most welcome.

Thanks in advance.

Alp

Tony Toews

2006-02-06, 8:26 pm

"Alp Bekisoglu" <alp@access_ng.com> wrote:

>Might sound a bit confusing but; I'm trying to use A2K db FE/BE but with 2
>backends. One is more sensitive data (financial) which I need to keep
>undistributed. In the main server both will be present (head office). But
>for the branch office the #2 BE will not be copied. I am using Peter
>Vukovic's Reconnect() function to ensure proper be connectivity.
>
>The scenario is when the second BE is not present, all related forms are
>inaccessible too so if I can rid any errors on Reconnect, I should be safe.
>Even the related menu options are unavailable when db accessed by machines
>outside the scope.
>
>Is this do'able via VBA? If so, any help/pointers is most welcome.

Sure, just open a recordset against those sensitive MDBs. If you get
an error then in your switchboard form don't allow uses to open the
sensitive forms.

And for that matter only enable the command buttons if the recordset
open is successful. That way if the users can't see the buttons
they're less likely to be irritated by thoughts of why they can't see
the data. <smile>

Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm

Alp Bekisoglu

2006-02-13, 9:24 am

Hi Tony,

Sorry for the late response. First, thanks for your suggestion.

Situation is:
Most of my forms are accessed via usermenu (a custom menu) where the
relevant forms are under disabled menu items if the application is run by
other machines/users. Thus the dim menu item is there but they will not be
able to do anything anyway.

My main problem is the fact that the Reconnect function returns error if it
can not locate a table in the backend. I'm afraid it will be the same if the
function can not even locate the backend at all. Na this is what I'm trying
to avoid.

I intend to come up with some code that will check the backends if they
exist, then only connect the one that is available and do away with the
missing one.

Do'able?

Thanks in advance,

Alp

"Tony Toews" <ttoews@telusplanet.net> wrote in message
news:qn9fu1p1dkbf5ah
fecpr3lh1klsh6965r6@
4ax.com...
> "Alp Bekisoglu" <alp@access_ng.com> wrote:
>
>
> Sure, just open a recordset against those sensitive MDBs. If you get
> an error then in your switchboard form don't allow uses to open the
> sensitive forms.
>
> And for that matter only enable the command buttons if the recordset
> open is successful. That way if the users can't see the buttons
> they're less likely to be irritated by thoughts of why they can't see
> the data. <smile>
>
> Tony
> --
> Tony Toews, Microsoft Access MVP
> Please respond only in the newsgroups so that others can
> read the entire thread of messages.
> Microsoft Access Links, Hints, Tips & Accounting Systems at
> http://www.granite.ab.ca/accsmstr.htm

Tony Toews

2006-02-14, 8:26 pm

"Alp Bekisoglu" <alp@access_ng.com> wrote:

>My main problem is the fact that the Reconnect function returns error if it
>can not locate a table in the backend. I'm afraid it will be the same if the
>function can not even locate the backend at all. Na this is what I'm trying
>to avoid.

So you'll have to muck about with the Reconnect function to not relink
those tables from the sensitive MDB

>I intend to come up with some code that will check the backends if they
>exist, then only connect the one that is available and do away with the
>missing one.

Open a recordset in your code against the sensitive MDB. Trap for the
error, whatever it is, in the error handling routine. If no error
then it's fine. If an error, whatever the four digit number is, then
it's not accessible.

Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm

Sponsored Links