S
Stewart Berman
We have an application split into a front end (code, queries, forms, macros)
and a back end (primarily tables).
The application is distributed in compiled form and is installed with the
Access 2007 Runtime package.
Part of the process occasional opens the back end directly in Runtime.
We normally distribute updates to the application by sending out a new front
end. Occasionally, an update will require a new table in the back end which
the front end will create.
The problem we have run into is that following sequence crashes the back
end:
1. An update is run that adds one or more tables to the back end.
2. The back end is opened and closed.
3. Another update is run that adds one or more tables to the back
end.
4. The back end is opened and crashes.
What is strange is that if the database is opened using a full version of
Access 2007 after before step (4) the back end can be opened in Runtime.
We have tried three methods for creating tables in the back end:
1. Create a database object connected to the back end and run create
table SQL.
2. Create a database object connected to the back end and create the
table in code. (i.e. db.createtable, etc.)
3. Use a DoCmd.TransferDatabase to transfer a copy of a table in the
front end to the back end.
All three results in the same crash after the second update is run.
This is 100% reproducible starting with a brand new back end database with
nothing in it.
Is this a known bug? Is there anyway around this?
and a back end (primarily tables).
The application is distributed in compiled form and is installed with the
Access 2007 Runtime package.
Part of the process occasional opens the back end directly in Runtime.
We normally distribute updates to the application by sending out a new front
end. Occasionally, an update will require a new table in the back end which
the front end will create.
The problem we have run into is that following sequence crashes the back
end:
1. An update is run that adds one or more tables to the back end.
2. The back end is opened and closed.
3. Another update is run that adds one or more tables to the back
end.
4. The back end is opened and crashes.
What is strange is that if the database is opened using a full version of
Access 2007 after before step (4) the back end can be opened in Runtime.
We have tried three methods for creating tables in the back end:
1. Create a database object connected to the back end and run create
table SQL.
2. Create a database object connected to the back end and create the
table in code. (i.e. db.createtable, etc.)
3. Use a DoCmd.TransferDatabase to transfer a copy of a table in the
front end to the back end.
All three results in the same crash after the second update is run.
This is 100% reproducible starting with a brand new back end database with
nothing in it.
Is this a known bug? Is there anyway around this?