tai su tusciom lentelem

"news"  wrote in message news:o57g0m$hj4$1@trimpas.omnitel.net...

deja sharinti info negalime :(


"Linas Petkevicius" <linas@NONONOlekiam.lt> wrote in message
news:o57fqt$hd6$1@trimpas.omnitel.net...
> Jei nelabai kondiencialu - gal gali permest ta db emeilu?
>
> "news"  wrote in message news:o57fp5$hbj$1@trimpas.omnitel.net...
>
> Deja deja..... niekas nepadejo..
>
> aciu bandziusiems
>
> gal kas zino kas galetu live paziureti ir isspresti
>
> VLN, shiaurinis
>
>
> "Laimis" <wiela@centras.lt> wrote in message
> news:o55vth$2dh$1@trimpas.omnitel.net...
>> news rase:
>>> neveikia jokie guzikai is menu lango,meta ta pacia lenta
>>>
>>> viskas tas pats, versijos ir os ir t.t.
>>
>>
>>
>> "A problem occurred while Microsoft Access was communicating with the OLE 
>> server or ActiveX Control. Close the OLE server and restart it outside of 
>> Microsoft Access. Then try the original operation again in Microsoft 
>> Access."
>>
>> Usually if the app will open on some computers, but not others, the 
>> problem is with the local database that Access uses to cache the server 
>> objects (so it doesn't have to download them every time you open the 
>> application).  If something has gone wrong with the cache database, you 
>> may see this error.
>>
>> If that is the problem, you can resolve this issue by deleting the local 
>> cached database for the app.  It will get recreated when you 'Customize 
>> in Access' again.  You can find the cache database at:
>>
>>     C:\users\username\AppData\Local\Microsoft\Access\DatabaseCache\15.0
>>
>>     The file will be named "appname on server.accdb" (italics replaced 
>> with your user/app/server name
>>
>> Software Engineer - Microsoft Corporation
>>
>>
>