plantage access

%3CLINGO-SUB%20id%3D%22lingo-sub-1970556%22%20slang%3D%22fr-FR%22%3Eaccess%20crash%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1970556%22%20slang%3D%22fr-FR%22%3E%3CP%3EHi%20all%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20have%20a%20split%20base%20access%20365%20mso%2016.0.13426.%2064%20bit.When%20I%20want%20to%20edit%20a%20macro%20the%20front%20plant%20(this%20on%20all%20posts)%2C%20no%20error%20message%20is%20returned.%20I%20can%20easily%20edit%20a%20report%2C%20a%20query%2C%20a%20module%2C%20a%20form.%3C%2FP%3E%3CP%3EThank%20you%20for%20your%20help%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-1970556%22%20slang%3D%22fr-FR%22%3E%3CLINGO-LABEL%3EAccess%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1970719%22%20slang%3D%22en-US%22%3ERe%3A%20plantage%20access%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1970719%22%20slang%3D%22en-US%22%3EHave%20you%20performed%20an%20Office%20Repair%3F%3CBR%20%2F%3EWhen%20doing%20development%20are%20you%20using%20local%20copies%20of%20both%20the%20front-end%20and%20back-end%3F%3CBR%20%2F%3EDoes%20this%20happen%20for%20just%20one%20database%2C%20or%20so%20databases%3F%3CBR%20%2F%3EHave%20you%20tried%20reverting%20your%20build%20to%20another%20no%20to%20see%20if%20you%20can%20isolate%20the%20issue%20as%20a%20bug%3F%3CBR%20%2F%3EWhen%20was%20the%20last%20time%20you%20compact%20or%20decompiled%20your%20database%3F%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1970886%22%20slang%3D%22fr-FR%22%3ERe%3A%20crash%20access%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1970886%22%20slang%3D%22fr-FR%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F459380%22%20target%3D%22_blank%22%3E%40Daniel_Pineault%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3Eafter%20complete%20repair%2C%20compaction%2C%20decompiles%20the%20problem%20is%20the%20same%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3Edevelopment%3A%20macros%20were%20developed%20when%20the%20base%20was%20not%20split%2C%20but%20they%20worked%20smoothly%20after%20splitting%2C%20suddenly%20for%206%20months%20more%20editing%20possible%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20only%20have%20one%20base%20with%20macros%2C%20so%20I%20can't%20see%20if%20the%20problem%20is%20reproducible%3C%2FP%3E%3CP%3EBack%20to%20a%20build%3A%20you%20mean%20a%20version%20downgrade%2C%20how%20to%20do%20it%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E
New Contributor

bonjour à tous,

 

J'ai une base fractionnée access 365 mso 16.0.13426. 64 bit.Lorsque je veux éditer une macro le frontale plante (ceci sur tous les postes), aucun message d'erreur n'est renvoyé. Je peux éditer sans problème un état, une requête, un module, un formulaire.

Merci de votre aide

2 Replies

Have you performed an Office Repair?
When doing development are you using local copies of both the front-end and back-end?
Does this happen for just one database, or all

 databases?
Have you tried reverting your build to another no to see if you can isolate the issue as a bug?
When was the last time you compact or decompiled your database?

@Daniel_Pineault 

après réparation complète, compactage, decompile le problème est le même

 

développement : les macros ont été développés lorsque la base n'était pas fractionnée, mais elles fonctionnaient sans problème après le fractionnement, subitement depuis 6 mois plus d'édition possible

 

Je n'ai qu'une seule base avec des macros, je ne peux donc voir si le problème est reproductible

Revenir à un build : vous voulez dire un downgrade de version, comment faire ?