Thank you Dave,
Of course i have imagined to put my temp tables in the local front end file
but this solution should increase the difficulties elsewhere.
As well as it does not explain why i get the trouble now running on Access
2002 runtime an not with applications running under Access 2000 runtime.
--
Programmer c''''''''est engager une partie d''''''''échecs contre un
adversaire plus fort que soi mais que l''''''''on finira toujours par vaincre
"Dave Patrick" wrote:
[Quoted Text] > I do that sometimes as well but I create the temp tables in the user's local > frontend not in a shared backend. That seems a waste of bandwidth and would > slow down the user's experience. > > -- > > Regards, > > Dave Patrick ....Please no email replies - reply in newsgroup. > Microsoft Certified Professional > Microsoft MVP [Windows] > http://www.microsoft.com/protect> > "Pugnace" wrote: > | I'm used to use "temporary tables" in a shared database containing only > | datas. I never had problem with this technic when my application was > running > | under Access2000 runtime but since i have upgraded to Access 2002 the > | database is broken near each day! > | The technic consist of creating a table at any running time mainly to > become > | the datasource of a form or a report then deleting it when the form or > report > | close. > | Each user creates and deletes its own tables and the total amount of > | temporary tables can reach up to 30. > | Do anyone know if the failure can come from this technic ? > | -- > | Programmer c''''''''est engager une partie d''''''''échecs contre un > | adversaire plus fort que soi mais que l''''''''on finira toujours par > vaincre > > > |