OpenReport cancelled

[wharting]

Hi,

I've a question concerning a report preview loaded from a form.
I'm building a database for complaint registration in Access 2003.
Herefore I've build a mainmenu and sub menus.


One of the submenu's opens a menu for reporting actions.

On my desktop it works fine and it does eveything I want to do.
But, on the network where I stored the database (for multi using), an other user then myself gets a message that OpenReport is cancelled after clicking a certian reportbutton. It simply won't open the report.
Can someone tell me why a report will open when I use the DB myself but won't if an other user try this?
Any help would be appreciated. Thanks in advance.

Best regards, Willem

[RuralGuy]

That often means you have misspelled something in the arguments of the OpenReport command.

[wharting]

That often means you have misspelled something in the arguments of the OpenReport command.

Ok, I understand. But when I (creator) use the DB and click the involved report, it works fine. Only other users have the problem that the requested report won't appear. So, if something should be misspelled, it shouldn't work for me too. right?

Reg.,
Willem

[RuralGuy]

Others may have Reference issues as well: http://www.btabdevelopment.com/ts/missref

[wharting]

Others may have Reference issues as well: http://www.btabdevelopment.com/ts/missref

Thanks RuralGuy . I'll try/investigate this next monday.
I'll be back to you.

Reg.,
Willem

[wharting]

Hi RuralGuy,

I've looked yesterday to the reference issues but every needed reference is present.
I also tried to include several others references but that didn't work either.
I've checked the source code and deleted code from no longer excisting routines.
I really don't know what to do now

Reg.,
Willem

[wharting]

Maybe spliting the DB in a FE and BE part will solve this issue.
Nice job for tonight.
to be continued.

[wharting]

I split the db in a be and fe part.
When another user then myself use the fe part, he/she gets the message that 'the object can't be found'. I checked pathname's and so on, and everything seems to be correct. I'm stuck now.

[RuralGuy]

Have you implemented User Level Security on this db?

[boblarson]

make sure that each user has read/write/delete rights for the folder where the backend is stored and also where the frontend is located that they are running it from.

[wharting]

@RuralGuy: There's no user level security on this db.

@BobLarson: the BE is stored in a folder where a small selection of users have read/write/create and delete rights. The FE is stored on the same network but in a user folder with the same rights as the BE folder.

Is it possible that somewhere in the source of the FE part a path is defined? I've searched for it but could not find it. Although I know really something of Access, I'm not a specialist and have my limitations about this . So it's possible I searched in the wrong part/place.

[boblarson]

@BobLarson: the BE is stored in a folder where a small selection of users have read/write/create and delete rights.

So, do you mean that ALL users of this database have the read/write/create and delete rights but other people do not. All users of the database need to have those full rights on the folder where the file exits.

Also for multiple users, you NEED to have EACH USER to have a COPY OF THE DATABASE frontend ON THEIR MACHINE. You don't run the frontend from a network location, if at all possible and you DO NOT have multiple people opening the same exact frontend file as that will cause problems as well as increasing the odds greatly for corruption.

[wharting]

So, do you mean that ALL users of this database have the read/write/create and delete rights but other people do not. All users of the database need to have those full rights on the folder where the file exits.

Also for multiple users, you NEED to have EACH USER to have a COPY OF THE DATABASE frontend ON THEIR MACHINE. You don't run the frontend from a network location, if at all possible and you DO NOT have multiple people opening the same exact frontend file as that will cause problems as well as increasing the odds greatly for corruption.

All users have access to the db with all rights.

I'll try to install the FE part in a folder on the c:drive instead of their personal environment on the network and see what will happen.
To be continued.

[wharting]

After cleaning up the mess in the DB, a new compiling and installation on the harddrive of each computer, the program with all the components works for every user.

Both RuralGuy and BobLarson, many thanks for your help
Best regards,
Willem ;-)

[RuralGuy]

Thanks for posting back with your success and solution.