Cannot open database because VBA projekt cannot be read

[Lilian]

Hi!
In my database which is connected to the server and have approximately 15
users begin appears warning message(during autorization) which looks like
this:"Cannot open the database because VBA projekt cannot be read".
As it looks like the VBA projekt is corrupted? What to do to prevent this
warning message?
Will be very appriciated for any tips.
Best regars,
Lilian

 

[Gina Whipp]

Lilian,

Before you look at preventing the warning message you need to determine what
is causing this message. I would start by looking at the VBA project. I
would also...

1. Make sure you have the below declarations in each and every module...

Option Compare Database
Option Explicit

2. Make sure you Compiled your database. If there are any errors repair
those and keep Compiling until all errors are fixed.

3. You say you are connected to a server. What kind of server, ie: SQL
Server, etc...?

4. As you don't mention what kind of server and I am not going to make an
assumption, is your database split? AND does everyone have their own front
end?

Answering the above will go a long way to determining what is going on...

--
Gina Whipp

"I feel I have been denied critical, need to know, information!" - Tremors
II

http://www.regina-whipp.com/index_files/TipList.htm

 

[Lilian]

Hi Gina!
Thank you very much for your answer.
My database is splitted to back-end and front-end and connected to local
server.(I don't use the SQL server).
both parts back-end, front-end, end security mdw is located on the server.
Users have only a shortcut on their computers. Back-end file is located
separate from front-end and security.mdw due to security reasons. I know that
is best to locate the front-end file hos client computer but they don't want
so. It doesn't seem to be a problem with vba project every procedure is
declared.
Probably the problem is that both parts of database is located on the server?
Best regards,
Lilian



"Gina Whipp" skrev:

 

[Gina Whipp]

Lilian,

Is everyone sharing the same front end? And I didn't see were you compiled
to insure no problems, have you done that?

--
Gina Whipp

"I feel I have been denied critical, need to know, information!" - Tremors
II

http://www.regina-whipp.com/index_files/TipList.htm

 

[Lilian]

Hi Gina!
Yes everyone is sharing the same front-end. Yes I did compiling -no
problems. What can cause this warning message I don't know.
Best regards,
Lilian


"Gina Whipp" skrev:

 

[John W. Vinson]

Yes everyone is sharing the same front-end

That configuration gives you all of the disadvantages of an unsplit database
AND of a properly split database, none of the advantages of splitting, and is
an almost guaranteed recipe for corruption.

If your IT people won't let the database be installed on the user's machines,
at least give each user thier own directory and their own copy of the
frontend.

 

[Gina Whipp]

Lilian,

To add to what John said... Is Name AutoCorrect turned off? I would also
take a look at...

http://allenbrowne.com/ser-47.html ...as there are some other items that
you might try.

--
Gina Whipp

"I feel I have been denied critical, need to know, information!" - Tremors
II

http://www.regina-whipp.com/index_files/TipList.htm