Error Mylti-User

[calvinle]

I have removed all the bad record and reimport the data. 1 of the user was not able to add new data. I went directly to the table to add that same data and it works. Then, that user is able to add more data now.

I will see if that #Error keeps coming back.



However, did you have a chance to look at my code? Is there anything wrong with the code??

 

[GinaWhipp]

Is it the same User as before? Does everyone have their own Frontend?

 

[calvinle]

Yes, I did not add any new user yet. There is a version in the LAN, however I have put a code to prevent them from opening from the LAN, so yes, everyone has their own frontend.

 

[GinaWhipp]

So, no other User had this problem only the same one... Please check their connection to the Network, sounds like there might be a problem there.

 

[calvinle]

Wow, and now, the old problem came back. It prompt Invalid Bookmark, and then, 4 lines becames #Error. I open the backend, and it says, Access has to repair the error. It then générâtes a report.

View attachment MSysCompactError.zip

 

[GinaWhipp]

Okay, let's try this... import all the Objects from ALL files into clean databases.

 

[calvinle]

How about the data??

Everytime that happen, it replaces all the data into #Error, so I don't know what the user had input in there anymore. I am losing data..

Here is the last error I received:

 

[GinaWhipp]

Yes, bring the data in the Tables AFTER you compact and Repair.

 

[calvinle]

Do you think changing the continuous back to dataview will solve the problem? I did make a test, and it looks like quicker in dataview than continuous.

 

[GinaWhipp]

It shouldn't matter... have you imported ALL the Objects and tested again?

 

[calvinle]

The error does not appear when only 1 user add data. I didn't have the chance to have my user testing it yet.
It's also hard for me to retest that way as my table are related to another table. I will have to manually readd all the related data which is long.
I will test it tomorrow with another user trying to add data both them and me at the same time.

 

[GinaWhipp]

And while you are doing that... did you make the other changes I requested earlier?

 

[calvinle]

I did not have the chance to do all that today. What I've said earlier what the experience the whole time last week and this morning until the crash. I had to stop the user to use the database to enter new data today until I find the fix.

 

[calvinle]

I have a feeling that it's the LAN problem. The speed that takes to save the record to the backend in the LAN for each user. The interference of the connectivity causes that. I will be leaving on vacation this thursday, so if I cannot find the fix, I will have create 1 table per user... :/

 

[GinaWhipp]

I have a feeling also but still want to rule out all other possibilities...

 

[calvinle]

Hi,

I have made a quick sample to check the possibilities of the problem.
I have created a new database with a backend of a sample table connected to the LAN, and subform without any coding. So the data entered by the user and me will feed to the backend. The test went well and even at high speed of entering data to it, no bug.
I have done another test, but in a filtered mode, the test went well with no bug.
I have done another test, using the link parent & child to a combobox, it works at slow speed, then fail at high speed.

I guess the problem is the link parent & child vs the LAN.

 

[GinaWhipp]

Did you switch to using Me. instead of Parent? Because that should not fail.

 

[calvinle]

Yes i did.!

 

[GinaWhipp]

Please upload what you have now and let me see if I can spot something because that should not be failing...

 

[calvinle]

Now the tool bugs again. I don't think it's necessary to spend more effort on this.
I am now thinking of 2 other ways, can you provide your feedback?
The user will have their own frontend.
On the main form there will be 2 button, 1 for add data, 1 for view data.
In the add data form, the data will be entered in local table, and once form is close also via a command save button, the data will be save to backend regardless the PK of local table, so the PK in backend will be created automatically.
Also, when someone is saving data to backend=only 1 connection at a time is allowed. If already connection already existed, which mean someone is saving on the backend, it will prompt the second user to wait until the save is completed.
There is the view form which is the same except no add allow, only edit.

What do you think?