| Author |
Topic |
|
X002548
Not Just a Number
15586 Posts |
 Posted - 2003-07-01 : 10:14:47
|
| Walking through a release procedure for an Access front end.Rockect Science Boy is telling me that he creates a blank Access database (as reccommended by MS) and imports all of the objects to the new blank database.I don't believe it. The overhead is huge and the I believe it's fraught with un-needed risks?Anyone with experience with this?He then creates an MDE after this and is then pushed via DNX to the clients.AAAAAAAAAAAAAAAHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHBrett8-) |
|
|
robvolk
Most Valuable Yak
15732 Posts |
Posted - 2003-07-01 : 13:22:43
|
| I don't think there's a lot of overhead to this, in fact it has the benefit of not copying over the fragmented version of tables, reports, forms, etc. and all the junk that clutters up an uncompacted MDB file. It's less than optimal, but if all of the tables are linked tables then it's not all that bad. The only thing that doesn't covert are the database properties (startup form, app name, some object visibilities)Still, you should have an empty template MDB or MDE that can be sent out, without having to re-create it each time. |
 |
|
|
X002548
Not Just a Number
15586 Posts |
Posted - 2003-07-01 : 13:46:45
|
| And don't forget security...I had to sit and watch him reassign to all of the objects...Plus He was getting error because main forms referencing sub forms that didn't import yet...but he said that as long as you hit ok within a minute, but after that it would be corrupted.He just doesn't believe in repair and compact (and because 2000's menu has it the other way around, he believe it does a compact and a repair).AAAAAAAAAAAAAAAAAAAAAHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHBrett8-) |
|
|
|
JimL
SQL Slinging Yak Ranger
1537 Posts |
Posted - 2003-07-01 : 14:09:10
|
| One thing to watch on linked Mdb tables, If The Primary of the mdb is compacted, all the apps will loose the link. This is the primary reason I changed over our backend to SQL.Note: you can callup a compact and repair on linked tables but it does not actually perform this. To repair or compact a linked mdb table you must open the primary exclusive...... Then all associated apps loose the path because Access totaly re-writes the table in a new loaction with a new header. JimUsers <> LogicEdited by - jiml on 07/01/2003 14:14:26 |
|
|
|
mohdowais
Sheikh of Yak Knowledge
1456 Posts |
Posted - 2003-07-01 : 14:42:28
|
| Hey brett, this guy seems to be causing you trouble no-end. Its about time you shipped this guy to the Empty Quarter....or send him here, and I can arrange a desert safari that accidently returns with one member less...MWAHAHAHAHAHA!! |
|
|
|
jsmith8858
Dr. Cross Join
7423 Posts |
Posted - 2003-07-01 : 15:32:07
|
quote:
One thing to watch on linked Mdb tables, If The Primary of the mdb is compacted, all the apps will loose the link..... Then all associated apps loose the path because Access totaly re-writes the table in a new loaction with a new header.
Are you sure about this? I do this all the time. When it compacts or repairs, it creates a temp copy off to the side, then deletes the original and replaces that with the newly optimized one. All links TO that database that was compacted or repaired work just fine. Which version of Access are you using? can you give an example?also:quote:
Note: you can callup a compact and repair on linked tables but it does not actually perform this.
What do you mean by that -- "callup" a compact and repair on a linked table? That isn't a command that acts upon a highlighted object in your database (i.e., a table or query) -- it always runs on whatever DB you have open. Can you explain more?Sorry, just curious ...- Jeff |
|
|
|
X002548
Not Just a Number
15586 Posts |
Posted - 2003-07-01 : 15:36:41
|
| Yeah no SH-T....Rocket Science Boy...(That's a referemce to my transitioner)To the nth level...and BEYOND!!!Jim, the tables are all SQL Server, Oh but of course he has a "version" table in Access. Why, just to make sure nothing done the same wat twuce...Know how many rows in the version table? for a 2 year old product?5 Hundred (gosh darn mother fupping) 28 rows.Now come on, lets get serious. What'd he have a release an hour?After transition I'm going to put a stop to any developemnt. If it breaks I'll (try) to fix it.In the mean time, I'm making a push for a new java/websphere/sql 2000 thin client application.Hell he even wrote like 7 DLLs...Why? (see above)AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHmmm...a desert adventure.....Brett8-)Edited by - x002548 on 07/01/2003 15:39:28Edited by - x002548 on 07/01/2003 15:40:30 |
|
|
|
JimL
SQL Slinging Yak Ranger
1537 Posts |
Posted - 2003-07-01 : 16:05:08
|
| If your Access.mdb tables for an application are linked and not primary (as they should be in a shared db environment)…...If you attempt a repair on a failed DB at the application, the system will not let you. You must open the Primary “Exclusive” in order to in act a repair. If you call a compact at the application, the system will act like it is repairing and compacting. However if you check the Primary’s Size (ours Is located on the main server) The db has not actually changed size.If you open the Access Primary “Exclusive” and compact the database, any local applications that have linked Tables will lose that connection.The Primary DB format is 97 the applications are a mix of 97,2000,XP. Note: Never attempt to repair a 97 version db with XP, it appears to repair the db but does all kinds of strange things to the data and format. I will be so Glad to get my final Data collection Applications off .mdb and over to SQL!!!!!!!!!!!!!!JimUsers <> Logic |
|
|
|
robvolk
Most Valuable Yak
15732 Posts |
Posted - 2003-07-01 : 19:21:39
|
quote:
If you open the Access Primary “Exclusive” and compact the database, any local applications that have linked Tables will lose that connection.
That's odd, I've NEVER seen this happen, unless it's particular to Access 2000 or higher. 97 never did that. In any case, the Linked Table Manager can re-establish the links without any trouble. And, of course, it makes no difference if all the linked tables are SQL Server. |
|
|
|
JimL
SQL Slinging Yak Ranger
1537 Posts |
Posted - 2003-07-02 : 10:43:06
|
| Linked table manager is not available to published applications.So I would be Relinking about 35 applications at the deveopment level, republishing and redistributing them to 50 users. Not what I would call a productive week.JimUsers <> Logic |
|
|
|
X002548
Not Just a Number
15586 Posts |
Posted - 2003-07-02 : 10:50:32
|
| Did I mention I hate Access (only because of what people want to do with it). Otherwise I love it for little things...kind of like a calculator.But with DTS, a play server, I don't even need it for those things anymore.1 thing it's great for is for eliminating end users creating excel spreadsheets I have to load.I mail them an access db, that has a table defined that matches a table I have to load, through "constraints" around it and then as autoform so the can do entry.It's 11:00amest and I've been on a conf call since 9am est working with the rocket boy trying just produce a releaseable app...import all new objects, reset security, relink tables, set database option..yada yada yadaThe reason we're doing this...BECASUE he read somewhere that this was the model to use...AAAAAAAAAAAAAAAAAAAAAAAAAAAAHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHCan't wait for the weekendBrett8-) |
|
|
|
JimL
SQL Slinging Yak Ranger
1537 Posts |
Posted - 2003-07-02 : 11:15:21
|
| That Desert trip is sounding more resonable all the timeJimUsers <> Logic |
|
|
|
X002548
Not Just a Number
15586 Posts |
Posted - 2003-07-02 : 11:29:17
|
| owais,When's the next trip scheduled?Brett8-) |
|
|
|
|
MS Access Front End Deployment