Error While opening the Access

Aleni

Registered User.
Local time
Yesterday, 20:54
Joined
Dec 6, 2012
Messages
45
Hi everyone!
This is the problem I am experiencing for the first time.

When I open my saved Database I am getting an error saying
"There was a problem sending the command to the program"

When I close it everything works normal.
Any one has any idea about this error?
Why I am getting this error?
 
Compact and Repair database, it should work :)
 
Thank you khodr.

I will try with it.
 
Hi Khodr I tried with Compact and Repair database.
But again it started to give the same error.
The error comes only if I open the database after few minutes.
When I first open I get the error and when I close and reopen I wont get error.

I am confused!
 
do you have autoexec macro in your database?
Check the onLoad event, did you try to compile your database?
check the on Open event,
compiling will reveal any problem could be with the code.
check those and revert.
hope you will solve it.
 
Thank you khodr.

I tried with compiling there is no problem.
But about autoexec macro I do not have any idea about it.
Please can you tell me briefly on what is that?
 
Autoexec macro is a Macro you create to setup your database startup behaviour, if you are the database creator and you don't know it that means you don't have it because we create the autoexec macro inside the databases,
a) are you trying to open your database via a network?
if So, check your network connection stability.....
b) are you using database as backend and frontend, if so, open the backend and close it again, just to elminate any temp file opened (that could happen when you force close database).
c)are you running your database via a network mapped hard drive?
if so then check your mapped drive capacity sometimes when the drive is full, loading the data could be slow and your database could be running some codes and the response could be slow from the back end, I feel this is too much I dont' want to confuse you, but these are the things I normally check when I get a wired problem with my databases, one last thing, try to run your database in a different computer and check if you still have the same problem.
Regards.
 
Last edited:
I am using database as backend and frontend, when i close and reopen i do not get any error.
But I am getting error if I open my database after few minutes.
I have no idea what's going on.
Anyways Thank you for help khodr
 
Lets go step by step
Press shift key while opening your database and open the main form manually and feedback if you still have the same problem,
In the file menu under options under current database in the application icon combo box did you selected any icon symbol for your database?
 
As of now there is no error as I told you the error is not coming frequently.
And even while pressing shift key its not giving any error.
Will let you know if I get the same error again.
About the application icon i did not select any icon symbol for my database.

Thank you.
 
Sometimes when you click to open this application from a folder and still remain on that folder means do not change the focus immediately after clicking the app icon, such error appears. Instead if you minimize that folder immediately after clicking the app icon, no error appears.

Does your case sound like this?

I faced this, but did not give much attention yet. But I have AutoExec and I feel that is causing something. Although that alarm is not critical & goes away easily.
 
Sometimes when you click to open this application from a folder and still remain on that folder means do not change the focus immediately after clicking the app icon, such error appears. Instead if you minimize that folder immediately after clicking the app icon, no error appears.

Does your case sound like this?

I faced this, but did not give much attention yet. But I have AutoExec and I feel that is causing something. Although that alarm is not critical & goes away easily.

Guys, Access will not generate an error without a reasons, sometimes reasons of errors could be irritating and it will drive us nervous to solve it, check your autoexec procedure sometimes you could have a problem in sorting the executable commands which might lead for an error, in all cases these kind of errors has so many reason that is why solving it takes time, but with programming you have to be patient to achieve the maximum,
 
Hi Mahenk and khodr!
Mahenk !
I was just worried if this error me problem in future because as khodr said Access will not generate an error without a reason.
But now i am not getting any error. I hope I will not face any problem in future also.
Thank you Khodr and mahenk.
 
I faced this, but did not give much attention yet. But I have AutoExec and I feel that is causing something. Although that alarm is not critical & goes away easily.

I did not mean that it is not required to resolve but I wanted to clear my situation why I am still with the problem and when I tell symptom, I donot know the solution.
Still, the best way I know to tackle such issue is to identify which are the events which cause trouble and disable one by one. But in this case problem is not regular, you may find difficult to track.

Anyway all the best for your project.
 
Actually i tried my best to solve but i do not know from where the problem was coming and yes, the problem is not regular which is a problem again.
But now I am not getting any such error message also and i just hope i will not get in future.

Thank you
 
Guys, we are not only dealing with access when we open the database, there is so many other staff working to view the output on our screen, when you run your database on a computer standalone sometimes because of low memory and the access are requesting a code to run and cannot get it on time then an error might generate itself because the code cannot cop with the memory, processor, or hard disk speed, sometimes we get errors if we have so many applications opened, databases running on the network sometimes they create errors because of the network folder settings we are using digital environment to run our databases and so many circumstances are there to help us if they don't cop well we won't get it fine
Finally we must always sort our problem correctly and logically and not always concentrate on the access and the code and the database check and inspect the whole environment always specially when we are sure that our code is correct and working fine on other people computers

One last tip : sometimes changing the database location from folder to another generate an error while opening and that is because access doesn't trust the location always add the database path to the trusted location center in your access program
Hope that helps
 
Last edited:

Users who are viewing this thread

Back
Top Bottom