Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
kiber
Starting Member
8 Posts |
 Posted - 2009-04-24 : 05:01:23
|
| Good morning. how can i create userform in sql? some people says me that create userform in PHP and connect your sql server... is it right? can i create userform in php or delphi and connect my sql server? I have 3 users from different region and i want to give them userform (interface). anD They fill information to userform connecting my server. and i see their information. That is my probler. I am new in this profession. I need help. |
|
|
nr
SQLTeam MVY
12543 Posts |
Posted - 2009-04-24 : 05:15:39
|
| php, delphi, c#.net, vb.net, .netnuc, asp.net, access, excel, .......There are lots of ways of creating client applications. It's usually best to do it in the tool you are most familiar with (which might be a problem for you).==========================================Cursors are useful if you don't know sql.DTS can be used in a similar way.Beer is not cold and it isn't fizzy. |
 |
|
|
kiber
Starting Member
8 Posts |
Posted - 2009-04-24 : 09:28:52
|
| thakns very much.I want to create cleint application for small insurance company. It has 4-5 branches. every branch has any information (statistics etc.). I want that all branch connect with main office (main database). you understand my idea probability.which is the best way? thanks again |
|
|
|
kiber
Starting Member
8 Posts |
Posted - 2009-04-27 : 00:52:29
|
| please, help me |
|
|
|
yonabout
Posting Yak Master
112 Posts |
Posted - 2009-04-27 : 12:52:24
|
| Hi Kiber,If you want your application to be useable and maintainable, you need to plan it out properly.When you're designing a database, you need to identify all the types of data you need to store (not forgetting that your application may generate data of its own that needs recording), then figure out how that data should be grouped together and use that as a basis for your table design. You then need to build the relationships between your tables.If you've got a solid database design, it really helps your application design because its much easier to define and write the classes that are going to read and update the data in your tables, and which will provide business logic and other functionality. An application based on a poorly designed database may work in the short term, but I can guarantee that it will start to cause weird behaviour, and become a maintainance nightmare before too long.like nr says, there are lots of ways of creating client applications, so if you've got no experience with any of these tools, I'd suggest you figure out what kind of applications you're most likely to be building (web / desktop / single tier / ntier etc.), read up on the development tools that sound like they'll let you do what you need to, then book yourself a training course or five.Cheers,Yonabout |
|
|
|
kiber
Starting Member
8 Posts |
Posted - 2009-04-27 : 14:18:13
|
| Thanks very much, Yonabout. |
|
|
|
kiber
Starting Member
8 Posts |
Posted - 2009-04-28 : 01:17:34
|
| I have one question also :)Is there own userform (forms like Access) in SQL Server? |
|
|
|
maeenul
Starting Member
20 Posts |
|
|
|
|
|
|
|
User Form