Re: A2007 convert ADP forms to MDB forms?
- From: NKTower <NKTower@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Fri, 6 Jun 2008 14:02:01 -0700
We had applied various hotfixes after the first tests, they didn't help. I
just returned to this post and see that it had some follow-up. For some
reason the "notify me" thing stopped. The link to hotfix published April 27
is clearly newer than our test, we'll have to try it.
The 2500 queries that are launched are after doing a single-column update
of a single row bound to a form - and a single record form at that. Can't
get simpler than that. SQL Profiler is referencing extended attributes and
it seems to launch queries touching most of our 130+ tables. Sincd same run
in Access 2003 didn't do any of that, we didn't dig much further. Gut feel
is that it touched attributes for every column in every table. (Most of
which are small lookup tables etc. perhaps a half dozen columns in 50 or so
rows.) I don't have the trace handy, I suppose we could regenerate it if we
really needed to so so. We have not explicitly touched or utilized any
extended attributes. Application started in Access 2003 with MSDE for
development, later SQL Server Express for development, SQL Server 2005 on
production servers. No problems there. Only when application was ported to
Access 2007 did it go bonkers.
"aaron.kempf@xxxxxxxxx" wrote:
have you tried these hotfixes?.
http://support.microsoft.com/kb/936519/en-us
-Aaron
On Mar 10, 2:01 pm, NKTower <NKTo...@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote:
We found a number of serious performance bugs in Acess 2007 ADP that didn't
get fixed in Office 2007 SP1. Application runs fine in Access 2003. Most
serious problem is that if we so much as touch a record source or execute an
on-the-fly query Access 2007 seems to instruct SQL Server takes it upon
itself to completely reconstruct the extended attribute tables - 2,700+
queries with about a 15 second delay before client becomes responsive again.
We are now looking at going back to MDB/DAO/ODBC as test bed works fine in
Access 2007. We found a script that was supposed to turn off this process
but it doesn't seem to help.
For the real application we have so far built a new front end with links to
the 100+ tables (trivial.) and brought modules and class modules across
(trivial again.) But we don't see a way to bring forms across.
So far we have tried:
a) Get External Data - IMPORT - chugs along naming some forms as it goes,
then crashes, leaving invisible Access 2007 task, need to boot. Upon opening
the forms container is empty.
b) COPY / PASTE at form level between two instances of Access - no go.
c) COPY/PASTE at design level between two instances of Access - no go.
d) removed record source property and tried a,b,c above - no go
e) Tried steps a,b,c,d above an XP Pro SP2 machine with Access 2003 instead
of Access 2007 - still no way to migrate forms.
So - is there a way to copy the forms out of an ADP into an MDB short of
complete manual reconstruction? We have 180 forms or subforms in the forms
container.
- Prev by Date: RE: Dynamic fields of query
- Next by Date: Re: Access 2007/SQL 2005 ADP Performance Issues
- Previous by thread: RE: Dynamic fields of query
- Next by thread: Anuncie seu Carro ou moto
- Index(es):
Relevant Pages
|
