Replica/Design master

[RuralGuy]

BTW, RG or Allan is just fine. Mr. Moderator is simply too formal. You are from the Philippines right?

[rommelgenlight]

already have done splitting it mr. moderator. but again, our concern is the continuity of records if the db has already exceeded its maximum size limit MS Access db as db.

[rommelgenlight]

already have done and tried splitting mr. moderator. but our concern again is the continuity of records if the ms access db has already exceeded its 2 gigabyte size limit.

you know mr. moderator, i knew this one head programmer of chevron, he told me that even a graduate of programming has a difficulty in making program. What more to non-programmers !

[rommelgenlight]

yes, I am from the Philippines. Sorry, I have no way to address you properly Allan.

[RuralGuy]

Does that mean you *have* split your application successfully?

[rommelgenlight]

yes. i have the frontend and backend db.

[RuralGuy]

Do you Compact and Repair on a regular basis?

[rommelgenlight]

yah. I have read probably most articles that can solve that problem. But I found none. I think the last recourse would be that request.

I really think that is possible coz they have increased MS ACCESS 97 size limit of 1 gigabyte to 2 gigabyte in MS ACCESS 2000.

Do you know why did they increased it? from 1 to 2 gig? what were the basis of increasing it?

[RuralGuy]

It requires a lot of changes internally to Access as far as the pointers are concerned. Do you have a db that has excedded the limits? Do you use Compact on Close?

[rommelgenlight]

yes. it is already exceeded 2 gig. so if it problems me, probably there are others too.

if there's a lot of changes to be done internally in access, I believe microsoft can handle it since THEY ARE microsoft, makers of great software products.

[RuralGuy]

Have you tried importing the tables to a new fresh db? There are solutions to your problem. I see now why you are so adamant about upping the limit.

[rommelgenlight]

im sorry i havent replied immediately. there is a power interruption here.

You said importing? I dont think importing would solve coz it is the same data and amount of data only transferred to new db. yes I am adamant coz they made the product and I believe they already know the structure of the db itself how to manipulate it. That's why I am convinced microsoft can do it and solve our problems.

The fact that they have upsized ms access 97 size limit of 1 gig to 2 gig in ms access 2000, therefore, they can do it.

[RuralGuy]

Have you tried the Jet Comp utility?

[rommelgenlight]

i dont think compacting would be the answer because i have tried it before, and I dont think it can compact the db much more.

[RuralGuy]

Have you tried the Jet Comp utility?

As I said, have you tried it?