Form's DataEntry Property

[ChrisTheIntern]

Hi peeps,

I have an issue with the DataEntry property causing my form to be only useable by one user at a time.

I've made a split database with the backend holding the survey response table on the slow company server, while the frontend is the survey form. It's been working fine although slow until I read somewhere that a dataentry form will load faster. I changed the form setting's DataEntry to "yes" and distributed the updated frontend copies but quickly found out that now only one user can have the form open at a time. After the first person opens the form, any other user that tries to open it fails to open anything and access goes "Not Responding" until I force it close.

Survey response table: PK = WorkOrder <-unique per survey
Fields: WorkOrder, Name, Date, A_Q01, A_Q02, A_Q03, ...

The data settings on the form is as follows:
Recordset Type: Dynaset
Fetch Defaults: Yes
Filter:
Filter On Load: No
Order By:
Order By on Load: No
Wait for Post Processing: No
Data Entry: Yes
Allow Additions: Yes
Allow Deletions: Yes
Allow Edits: Yes
Allow Filters: Yes
Record Locks: No Locks

There is also a subform on form which draws 3 fields from a query. The three fields on the subform are name, date, and number of issues. This subform is not linked and it is just a log of recent surveys.

I would like to use DataEntry Mode if possible because the form load time is currently 20 seconds without DataEntry. Does anyone know why this is not working for me?

If any more relevant information is needed, I am eager to provide and would very much appreciate any help I can get.

Thanks,
ChrisTheIntern

 

[spikepl]

I would like to use DataEntry Mode if possible because the form load time is currently 20 seconds without DataEntry.

This implies it takes a long time to get data from a table. The dataentry mode presumably entails that no previously existing data is read. This can also be accomplished by a query (and without setting dataentry mode) so show me the record source of that form and I can show you a query which does the same thing.(And no, I have no idea why there seems to be a collision with multiple users - I do not think that it should be so).

 

[ChrisTheIntern]

SELECT Responses.WO, Responses.Reviewer, Responses.[Review Date], Responses.[A_Q01], Responses.[A_Q02], Responses.[A_Q03], Responses.[A_Q04], Responses.[A_Q05] FROM Responses;

 

[spikepl]

Try this:

SELECT Responses.WO, Responses.Reviewer, Responses.[Review Date], Responses.[A_Q01], Responses.[A_Q02], Responses.[A_Q03], Responses.[A_Q04], Responses.[A_Q05] FROM Responses WHERE 1=0;

it makes sure that no old data is read, so just like DataEntry.

 

[ChrisTheIntern]

The query record source works great on the database when i split it locally but the form does not open when i split the back end to the server. Could it be an issue with the server not giving the same permissions as I would have locally?

 

[spikepl]

The query specifics are not related to being able to read from server backend, so taht is a different issue. Does it concern just this table or all tables or anything from server or what? (This is supposed to give you implied hints as to how to debug it).

 

[ChrisTheIntern]

My apologies, it works fine now and amazingly fast. 3 second load! However, the reason why I wanted to use the DataEntry property was so I can set it off when i use my Edit Survey button. I don't know how to do that with this query. However, this has shown me that a faster form is possible and I am relieved.

 

[spikepl]

1. You can change the form's Record Source property from what you had to the one I gave you and back - it's just a string, afterall.
2. You can have a parameter in the query set on the form, so

....WHERE 1=Forms!MyFormName!txtMyParameterName

so you could change a value in a visible or invisible textbox on the form called txtMyParameterName and then do a Me.Requery to re-run the query.

 

[ChrisTheIntern]

That will work! Thank you so much! This form is opened around 10 times a day by 3 people so you have saved us a ton of time.