No, that was his goal. To have one app leave behind a database that would be used by another app. If it is going to be used, it's not "wasted". Now if it gets left behind when that second app gets deleted you might have a point, which is why I suggested that the DB's creator ID match that of the second app. -- -Richard M. Hartman [EMAIL PROTECTED] 186,000 mi./sec ... not just a good idea, it's the LAW! > -----Original Message----- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] > > But now the DB won't be deleted when the app is. Leaving wasted > memory. Correct ? > > > <pre> > Thanks Alan & Richard! Setting my app's creator ID to be > different from > its database's creator ID did the trick. > > Michael > </pre> > > >
- creating a read-only database Michael McFarland
- Re: creating a read-only database Alan Pinstein
- Re: creating a read-only database Michael McFarland
- RE: creating a read-only database Richard Hartman
- Re: creating a read-only database Alan Pinstein
- Re: creating a read-only database Michael McFarland
- Re: creating a read-only database ron
- Re: creating a read-only database Richard Hartman
- Re: creating a read-only database Alan Pinstein
- RE: creating a read-only database Alan Pinstein
- Re: creating a read-only database Michael McFarland
- Re: creating a read-only database pete moss
- Re: creating a read-only database Roger Chaplin
- Re: creating a read-only database Michael McFarland
- Re: creating a read-only database Creative Digital Publishing Inc.
- Re: creating a read-only database S�rgio Carvalho
- Re: creating a read-only database Michael McFarland
