MikeAngelastro
Registered User.
- Local time
- Today, 08:03
- Joined
- Mar 3, 2000
- Messages
- 254
Hi,
We were using Terminal Services on a Windows 2000 Server machine to run an Access-based accounting system which I am customizing on a daily basis. After each change I made, I would compact and repair the MDB and then create an MDE. I would copy the MDE over to the server and there it would work as well as it did on my own machine (Windows XP).
We recently upgraded the server to Windows 2003 Server Enterprise edition. After the change we seem to be having weird problems on the server when the same program would work on my machine.
One problem was that in certain cases it would not print. Using the MDB equivalent of the MDE, I would find that the program did not know what to do with the "Me" designation when referring to a report. Creating an MDE on the server instead of my workstation seems to fix this problem. This problem has never occurred on my PC.
Another problem is that sometimes a sub form will not appear on a form when
the form is opened and the sub form has no record to show. Refreshing the form doesn't help. This problem does not appear to be helped by making the MDE on the server. I just noticed that when I open the parent table, Sales Orders, I am able to add records. But when I open the child table, Sales Order Line items, I am not able to add records. This is probably the reason. If the MDB resides on my workstation, I can add records to the Sales Order Line items table. If the MDB resides on the server, I can not add records to the Sales Order Line items table, even if I am looking at it on my workstation through the network. So it seems to be related to the machine that the database is residing on.
The inability to add records to a child table is pretty basic. Anyone else have these problems?
Thanks,
Mike
We were using Terminal Services on a Windows 2000 Server machine to run an Access-based accounting system which I am customizing on a daily basis. After each change I made, I would compact and repair the MDB and then create an MDE. I would copy the MDE over to the server and there it would work as well as it did on my own machine (Windows XP).
We recently upgraded the server to Windows 2003 Server Enterprise edition. After the change we seem to be having weird problems on the server when the same program would work on my machine.
One problem was that in certain cases it would not print. Using the MDB equivalent of the MDE, I would find that the program did not know what to do with the "Me" designation when referring to a report. Creating an MDE on the server instead of my workstation seems to fix this problem. This problem has never occurred on my PC.
Another problem is that sometimes a sub form will not appear on a form when
the form is opened and the sub form has no record to show. Refreshing the form doesn't help. This problem does not appear to be helped by making the MDE on the server. I just noticed that when I open the parent table, Sales Orders, I am able to add records. But when I open the child table, Sales Order Line items, I am not able to add records. This is probably the reason. If the MDB resides on my workstation, I can add records to the Sales Order Line items table. If the MDB resides on the server, I can not add records to the Sales Order Line items table, even if I am looking at it on my workstation through the network. So it seems to be related to the machine that the database is residing on.
The inability to add records to a child table is pretty basic. Anyone else have these problems?
Thanks,
Mike